Performance measurements related to application triggering and SMS over NAS

ABSTRACT

Techniques for performance measurements related to application triggering and short message service (SMS) over non-access stratum (NAS) including obtaining raw performance measurements from one or more network functions in a wireless communication network, the one or more network functions including at least one of a network exposure function (NEF) or an access and mobility management function (AMF), and generating performance measurements for the one or more network functions based on the raw performance measurements.

CROSS-REFERENCE TO RELATED APPLICATION

The present application is a U.S. National Phase application under 35U.S.C. § 371 of International Patent Application No. PCT/US2020/037528,filed on Jun. 12, 2020, which claims priority to U.S. Provisional PatentApplication No. 62/860,647, filed Jun. 12, 2019, the disclosures of eachof which are incorporated herein by reference in their entirety.

TECHNICAL FIELD

This disclosure relates generally to performance measurements inwireless communications.

BACKGROUND

Wireless communications have evolved significantly from early voicesystems to today's highly sophisticated integrated communicationplatform. The next generation wireless communication system, fifthgeneration new radio (5G NR), will expand wireless communications tousers operating vastly different and sometimes conflicting services andapplications. In general, 5G NR will evolve based on the thirdgeneration partnership project (3GPP) long term evolution advance(LTE-Advanced) standard with additional potential new radio accesstechnologies (RATs) to improve wireless connectivity solutions.

SUMMARY

In general, in an aspect, a method includes obtaining raw performancemeasurements from one or more network functions in a wirelesscommunication network, the one or more network functions including atleast one of a network exposure function (NEF) or an access and mobilitymanagement function (AMF), and generating performance measurements forthe one or more network functions based on the raw performancemeasurements.

In general, in an aspect, a processor for a telecommunications deviceincludes circuitry to execute one or more instructions that, whenexecuted, cause the processor to perform operations including: obtainingraw performance measurements from one or more network functions in awireless communication network, the one or more network functionsincluding at least one of a NEF or an AMF, and generating performancemeasurements for the one or more network functions based on the rawperformance measurements.

In general, in an aspect, a non-transitory computer readable storagemedium storing instructions which, when executed by one or moreprocessors, cause the one or more processors to perform operationsincluding: obtaining raw performance measurements from one or morenetwork functions in a wireless communication network, the one or morenetwork functions including at least one of a NEF or an AMF, andgenerating performance measurements for the one or more networkfunctions based on the raw performance measurements.

Implementations of any of the aspects can include one or a combinationof two or more of the following features.

In some examples, the one or more network functions are NEFs, and theperformance measurements are related to application triggering requestedby an application function. The performance measurements can include oneor more of a number of application trigger requests, a number ofapplication trigger requests accepted for delivery, a number ofapplication trigger requests rejected for delivery, a number of protocoldata unit (PDU) sessions requested to modify, or a number of applicationtrigger delivery reports. The number of application trigger requests canbe based on a cumulative counter that is triggered on receipt of adelivery request (e.g., a Nnef_Trigger_Delivery request) by a NEF fromthe application function. The number application trigger requestsaccepted for delivery can be based on a cumulative counter that istriggered on transmission of a delivery response (e.g., aNnef_trigger_Delivery response) by a NEF to the application function,with the delivery response including an indication that an applicationtrigger request has been accepted for delivery to a user equipment (UE).The number of application trigger requests rejected for delivery can bebased on a cumulative counter that is triggered on transmission of adelivery response (e.g., a Nnef_Trigger_Delivery response) by a NEF tothe application function, with the delivery response including anindication that an application trigger request has been rejected fordelivery to a UE. In some examples, the number of application triggerrequests rejected for delivery is incremented per error code (e.g., perresponse code, as specified in the 3GPP technical specifications). Thenumber of application trigger delivery reports can be based on acumulative counter that is triggered on transmission of a deliverymessage (e.g., a Nnef_Trigger_Delivery Notify message) by a NEF to theapplication function, with the delivery message including an indicationof a delivery result of an application trigger. In some examples, thenumber of application trigger delivery reports is incremented perdelivery result (e.g., success, failure, or another result specified inthe 3GPP technical specifications).

In some examples, the one or more network functions are AMFs, and theperformance measurements are related to short message service (SMS) overnon-access stratum (NAS). The performance measurements include one ormore of a number of registration requests for SMS over NAS, a number ofsuccessful registrations allowed for SMS over NAS, a number of attemptedmobile originated (MO) SMS messages over NAS, a number of MO SMSmessages successfully transported over NAS, a number of attempted mobileterminated (MT) SMS messages over NAS, or a number of MT SMS messagessuccessfully transported over NAS.

The number of registration requests for SMS over NAS can be based on acumulative counter that is triggered on receipt of a registrationrequest message by an AMF from a UE, the registration request messageincluding an indication that the UE supports SMS delivery over NAS. Thenumber of successful registrations allowed for SMS over NAS can be basedon a cumulative counter that is triggered on transmission of aregistration accept message by an AMF to a UE, the registration acceptmessage including an indication that the SMS is allowed.

The number of attempted MO SMS messages over NAS can be based on acumulative counter that is triggered on receipt of a NAS message by anAMF from a UE, the NAS message including an indication of SMStransportation. The number of MO SMS messages successfully transportedover NAS can be based on a cumulative counter that is triggered ontransmission of a NAS message by an AMF to a UE, the NAS messageincluding an indication that the MO SMS message has been successfullydelivered.

The number of attempted MT SMS messages over NAS can be based on acumulative counter that is triggered on transmission of a NAS message byan AMF to a UE, the NAS message including an indication of SMStransportation. The number of MT SMS messages successfully transportedover NAS can be based on a cumulative counter that is triggered onreceipt of a NAS message by an AMF from a UE, the NAS message includingan indication that the MT SMS message has been successfully delivered.

In some examples, the performance measurements is separated by accesstype (e.g., 3GPP access and non-3GPP access). In other examples, theperformance measurements are made without regard to the access type. Theraw performance measurements can be obtained, and the performancemeasurements can be generated, by a service producer that is located,for example, in one of the one or more NEFs, AMFs, or another managementfunction. The generated performance measurements can be stored,transmitted, displayed, or otherwise provided to end users (e.g.,service consumers) in any suitable form.

The details of one or more implementations are set forth in theaccompanying drawings and the description below. The techniquesdescribed here may be implemented by one or more wireless communicationsystems, components of a wireless communication system (e.g., a userequipment, a base station), or other systems, devices, methods, ornon-transitory computer-readable media, among others. Other features andadvantages will be apparent from the description and drawings, and fromthe claims.

BRIEF DESCRIPTION OF DRAWINGS

FIGS. 1-3 illustrate example wireless communication systems.

FIG. 4 illustrates an example of infrastructure equipment.

FIG. 5 illustrates an example of a platform or device.

FIG. 6 illustrates example components of baseband circuitry and radiofront end circuitry.

FIG. 7 illustrates example components of cellular communicationcircuitry.

FIG. 8 illustrates example protocol functions that may be implemented inwireless communication systems.

FIG. 9 illustrates example components of a core network.

FIG. 10 illustrates an example system to support network functionvirtualization.

FIG. 11 illustrates an example computer system.

FIG. 12 illustrates an example device triggering procedure.

FIG. 13 illustrates an example non-roaming architecture.

FIG. 14 illustrates an example performance management system.

FIG. 15 illustrates an example process for performance measurementsrelated to application triggering and SMS over NAS.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

The present disclosure provides techniques for generating performancemeasurements in wireless communication networks, such as 5G NR networks.In particular, the techniques described here provide for measuring theperformance of application triggering by network exposure functions(NEFs) and short message service (SMS) over non-access stratum (NAS) byaccess and mobility management functions (AMFs). In doing so, theperformance of application triggering and SMS over NAS can be monitoredto identify potential problems in the network or network interface, andperformance indicators can be provided to end users.

FIG. 1 illustrates an example wireless communication system 100. Forpurposes of convenience and without limitation, the example system 100is described in the context of the LTE and 5G NR communication standardsas defined by the 3GPP technical specifications. However, the technologydescribed herein may be implemented in other communication systems usingother communication standards, such as other 3GPP standards or IEEE802.16 protocols (e.g., WMAN or WiMAX), among others.

The system 100 includes UE 101 a and UE 101 b (collectively referred toas the “UEs 101”). In this example, the UEs 101 are illustrated assmartphones (e.g., handheld touchscreen mobile computing devicesconnectable to one or more cellular networks). In other examples, any ofthe UEs 101 may include other mobile or non-mobile computing devices,such as consumer electronics devices, cellular phones, smartphones,feature phones, tablet computers, wearable computer devices, personaldigital assistants (PDAs), pagers, wireless handsets, desktop computers,laptop computers, in-vehicle infotainment (IVI), in-car entertainment(ICE) devices, an Instrument Cluster (IC), head-up display (HUD)devices, onboard diagnostic (OBD) devices, dashtop mobile equipment(DME), mobile data terminals (MDTs), Electronic Engine Management System(EEMS), electronic/engine control units (ECUs), electronic/enginecontrol modules (ECMs), embedded systems, microcontrollers, controlmodules, engine management systems (EMS), networked or “smart”appliances, machine-type communications (MTC) devices,machine-to-machine (M2M) devices, Internet of Things (IoT) devices, orcombinations of them, among others.

In some examples, any of the UEs 101 may be IoT UEs, which can include anetwork access layer designed for low-power IoT applications utilizingshort-lived UE connections. An IoT UE can utilize technologies such asM2M or MTC for exchanging data with an MTC server or device using, forexample, a public land mobile network (PLMN), proximity services(ProSe), device-to-device (D2D) communication, sensor networks, IoTnetworks, or combinations of them, among others. The M2M or MTC exchangeof data may be a machine-initiated exchange of data. An IoT networkdescribes interconnecting IoT UEs, which may include uniquelyidentifiable embedded computing devices (within the Internetinfrastructure), with short-lived connections. The IoT UEs may executebackground applications (e.g., keep-alive messages or status updates) tofacilitate the connections of the IoT network.

The UEs 101 are configured to connect (e.g., communicatively couple)with an access network (AN) or radio access network (RAN) 110. In someexamples, the RAN 110 may be a next generation RAN (NG RAN), an evolvedUMTS terrestrial radio access network (E-UTRAN), or a legacy RAN, suchas a UNITS terrestrial radio access network (UTRAN) or a GSM EDGE radioaccess network (GERAN). As used herein, the term “NG RAN” may refer to aRAN 110 that operates in a 5G NR system 100, and the term “E-UTRAN” mayrefer to a RAN 110 that operates in an LTE or 4G system 100.

To connect to the RAN 110, the UEs 101 utilize connections (or channels)103 and 104, respectively, each of which may include a physicalcommunications interface or layer, as described below. In this example,the connections 103 and 104 are illustrated as an air interface toenable communicative coupling, and can be consistent with cellularcommunications protocols, such as a global system for mobilecommunications (GSM) protocol, a code-division multiple access (CDMA)network protocol, a push-to-talk (PTT) protocol, a PTT over cellular(POC) protocol, a universal mobile telecommunications system (UMTS)protocol, a 3GPP LTE protocol, a 5G NR protocol, or combinations ofthem, among other communication protocols. In some examples, the UEs 101may directly exchange communication data using an interface 105, such asa ProSe interface. The interface 105 may alternatively be referred to asa sidelink interface 105 and may include one or more logical channels,such as a physical sidelink control channel (PSCCH), a physical sidelinkshared channel (PSSCH), a physical sidelink downlink channel (PSDCH), ora physical sidelink broadcast channel (PSBCH), or combinations of them,among others.

The UE 101 b is shown to be configured to access an access point (AP)106 (also referred to as “WLAN node 106,” “WLAN 106,” “WLAN Termination106,” “WT 106” or the like) using a connection 107. The connection 107can include a local wireless connection, such as a connection consistentwith any IEEE 802.11 protocol, in which the AP 106 would include awireless fidelity (Wi-Fi®) router. In this example, the AP 106 is shownto be connected to the Internet without connecting to the core networkof the wireless system, as described in further detail below. In variousexamples, the UE 101 b, RAN 110, and AP 106 may be configured to useLTE-WLAN aggregation (LWA) operation or LTW/WLAN radio level integrationwith IPsec tunnel (LWIP) operation. The LWA operation may involve the UE101 b in RRC_CONNECTED being configured by a RAN node 111 a, 111 b toutilize radio resources of LTE and WLAN. LWIP operation may involve theUE 101 b using WLAN radio resources (e.g., connection 107) using IPsecprotocol tunneling to authenticate and encrypt packets (e.g., IPpackets) sent over the connection 107. IPsec tunneling may includeencapsulating the entirety of original IP packets and adding a newpacket header, thereby protecting the original header of the IP packets.

The RAN 110 can include one or more AN nodes or RAN nodes 111 a and 111b (collectively referred to as “RAN nodes 111” or “RAN node 111”) thatenable the connections 103 and 104. As used herein, the terms “accessnode,” “access point,” or the like may describe equipment that providesthe radio baseband functions for data or voice connectivity, or both,between a network and one or more users. These access nodes can bereferred to as base stations (BS), gNodeBs, gNBs, eNodeBs, eNBs, NodeBs,RAN nodes, rode side units (RSUs), transmission reception points (TRxPsor TRPs), and the link, and can include ground stations (e.g.,terrestrial access points) or satellite stations providing coveragewithin a geographic area (e.g., a cell), among others. As used herein,the term “NG RAN node” may refer to a RAN node 111 that operates in an5G NR system 100 (for example, a gNB), and the term “E-UTRAN node” mayrefer to a RAN node 111 that operates in an LTE or 4G system 100 (e.g.,an eNB). In some examples, the RAN nodes 111 may be implemented as oneor more of a dedicated physical device such as a macrocell base station,or a low power (LP) base station for providing femtocells, picocells orother like cells having smaller coverage areas, smaller user capacity,or higher bandwidth compared to macrocells.

In some examples, some or all of the RAN nodes 111 may be implemented asone or more software entities running on server computers as part of avirtual network, which may be referred to as a cloud RAN (CRAN) or avirtual baseband unit pool (vBBUP). The CRAN or vBBUP may implement aRAN function split, such as a packet data convergence protocol (PDCP)split in which radio resource control (RRC) and PDCP layers are operatedby the CRAN/vBBUP and other layer two (e.g., data link layer) protocolentities are operated by individual RAN nodes 111; a medium accesscontrol (MAC)/physical layer (PHY) split in which RRC, PDCP, MAC, andradio link control (RLC) layers are operated by the CRAN/vBBUP and thePHY layer is operated by individual RAN nodes 111; or a “lower PHY”split in which RRC, PDCP, RLC, and MAC layers and upper portions of thePHY layer are operated by the CRAN/vBBUP and lower portions of the PHYlayer are operated by individual RAN nodes 111. This virtualizedframework allows the freed-up processor cores of the RAN nodes 111 toperform, for example, other virtualized applications. In some examples,an individual RAN node 111 may represent individual gNB distributedunits (DUs) that are connected to a gNB central unit (CU) usingindividual F1 interfaces (not shown in FIG. 1 ). In some examples, thegNB-DUs may include one or more remote radio heads or RFEMs (see, e.g.,FIG. 4 ), and the gNB-CU may be operated by a server that is located inthe RAN 110 (not shown) or by a server pool in a similar manner as theCRAN/vBBUP. Additionally or alternatively, one or more of the RAN nodes111 may be next generation eNBs (ng-eNBs), including RAN nodes thatprovide E-UTRA user plane and control plane protocol terminations towardthe UEs 101, and are connected to a 5G core network (e.g., core network120) using a next generation interface.

In vehicle-to-everything (V2X) scenarios, one or more of the RAN nodes111 may be or act as RSUs. The term “Road Side Unit” or “RSU” refers toany transportation infrastructure entity used for V2X communications. ARSU may be implemented in or by a suitable RAN node or a stationary (orrelatively stationary) UE, where a RSU implemented in or by a UE may bereferred to as a “UE-type RSU,” a RSU implemented in or by an eNB may bereferred to as an “eNB-type RSU,” a RSU implemented in or by a gNB maybe referred to as a “gNB-type RSU,” and the like. In some examples, anRSU is a computing device coupled with radio frequency circuitry locatedon a roadside that provides connectivity support to passing vehicle UEs101 (vUEs 101). The RSU may also include internal data storage circuitryto store intersection map geometry, traffic statistics, media, as wellas applications or other software to sense and control ongoing vehicularand pedestrian traffic. The RSU may operate on the 5.9 GHz Direct ShortRange Communications (DSRC) band to provide very low latencycommunications required for high speed events, such as crash avoidance,traffic warnings, and the like. Additionally or alternatively, the RSUmay operate on the cellular V2X band to provide the aforementioned lowlatency communications, as well as other cellular communicationsservices. Additionally or alternatively, the RSU may operate as a Wi-Fihotspot (2.4 GHz band) or provide connectivity to one or more cellularnetworks to provide uplink and downlink communications, or both. Thecomputing device(s) and some or all of the radiofrequency circuitry ofthe RSU may be packaged in a weatherproof enclosure suitable for outdoorinstallation, and may include a network interface controller to providea wired connection (e.g., Ethernet) to a traffic signal controller or abackhaul network, or both.

Any of the RAN nodes 111 can terminate the air interface protocol andcan be the first point of contact for the UEs 101. In some examples, anyof the RAN nodes 111 can fulfill various logical functions for the RAN110 including, but not limited to, radio network controller (RNC)functions such as radio bearer management, uplink and downlink dynamicradio resource management and data packet scheduling, and mobilitymanagement.

In some examples, the UEs 101 can be configured to communicate usingorthogonal frequency division multiplexing (OFDM) communication signalswith each other or with any of the RAN nodes 111 over a multicarriercommunication channel in accordance with various communicationtechniques, such as, but not limited to, OFDMA communication techniques(e.g., for downlink communications) or SC-FDMA communication techniques(e.g., for uplink and ProSe or sidelink communications), although thescope of the techniques described here not limited in this respect. TheOFDM signals can comprise a plurality of orthogonal subcarriers.

In some examples, a downlink resource grid can be used for downlinktransmissions from any of the RAN nodes 111 to the UEs 101, while uplinktransmissions can utilize similar techniques. The grid can be atime-frequency grid, called a resource grid or time-frequency resourcegrid, which is the physical resource in the downlink in each slot. Sucha time-frequency plane representation is a common practice for OFDMsystems, which makes it intuitive for radio resource allocation. Eachcolumn and each row of the resource grid corresponds to one OFDM symboland one OFDM subcarrier, respectively. The duration of the resource gridin the time domain corresponds to one slot in a radio frame. Thesmallest time-frequency unit in a resource grid is denoted as a resourceelement. Each resource grid comprises a number of resource blocks, whichdescribe the mapping of certain physical channels to resource elements.Each resource block comprises a collection of resource elements; in thefrequency domain, this may represent the smallest quantity of resourcesthat currently can be allocated. There are several different physicaldownlink channels that are conveyed using such resource blocks.

In some examples, the UEs 101 and the RAN nodes 111 communicate (e.g.,transmit and receive) data over a licensed medium (also referred to asthe “licensed spectrum” or the “licensed band”) and an unlicensed sharedmedium (also referred to as the “unlicensed spectrum” or the “unlicensedband”). The licensed spectrum may include channels that operate in thefrequency range of approximately 400 MHz to approximately 3.8 GHz,whereas the unlicensed spectrum may include the 5 GHz band.

To operate in the unlicensed spectrum, the UEs 101 and the RAN nodes 111may operate using license assisted access (LAA), enhanced-LAA (eLAA), orfurther enhanced-LAA (feLAA) mechanisms. In these implementations, theUEs 101 and the RAN nodes 111 may perform one or more knownmedium-sensing operations or carrier-sensing operations, or both, todetermine whether one or more channels in the unlicensed spectrum areunavailable or otherwise occupied prior to transmitting in theunlicensed spectrum. The medium/carrier sensing operations may beperformed according to a listen-before-talk (LBT) protocol. LBT is amechanism in which equipment (for example, UEs 101, RAN nodes 111)senses a medium (for example, a channel or carrier frequency) andtransmits when the medium is sensed to be idle (or when a specificchannel in the medium is sensed to be unoccupied). The medium sensingoperation may include clear channel assessment (CCA), which uses energydetection to determine the presence or absence of other signals on achannel in order to determine if a channel is occupied or clear. ThisLBT mechanism allows cellular/LAA networks to coexist with incumbentsystems in the unlicensed spectrum and with other LAA networks. Energydetection may include sensing RF energy across an intended transmissionband for a period of time and comparing the sensed RF energy to apredefined or configured threshold.

The incumbent systems in the 5 GHz band can be WLANs based on IEEE802.11 technologies. WLAN employs a contention-based channel accessmechanism (e.g., CSMA with collision avoidance (CSMA/CA)). In someexamples, when a WLAN node (e.g., a mobile station (MS), such as UE 101,AP 106, or the like) intends to transmit, the WLAN node may firstperform CCA before transmission. Additionally, a backoff mechanism isused to avoid collisions in situations where more than one WLAN nodesenses the channel as idle and transmits at the same time. The backoffmechanism may be a counter that is drawn randomly within the contentionwindow size (CWS), which is increased exponentially upon the occurrenceof collision and reset to a minimum value as the transmission succeeds.In some examples, the LBT mechanism designed for LAA is similar to theCSMA/CA of WLAN. In some examples, the LBT procedure for DL or ULtransmission bursts, including PDSCH or PUSCH transmissions,respectively, may have an LAA contention window that is variable inlength between X and Y extended CAA (ECCA) slots, where X and Y areminimum and maximum values for the CWSs for LAA. In one example, theminimum CWS for an LAA transmission may be 9 microseconds (μs); however,the size of the CWS and a maximum channel occupancy time (for example, atransmission burst) may be based on governmental regulatoryrequirements.

In some examples, the LAA mechanisms are built on carrier aggregationtechnologies of LTE-Advanced systems. In CA, each aggregated carrier isreferred to as a component carrier. In some examples, a componentcarrier may have a bandwidth of 1.4, 3, 5, 10, 15 or 20 MHz, and amaximum of five component carriers can be aggregated to provide amaximum aggregated bandwidth is 100 MHz. In frequency division duplex(FDD) systems, the number of aggregated carriers can be different for DLand UL. For example, the number of UL component carriers can be equal toor lower than the number of DL component carriers. In some cases,individual component carriers can have a different bandwidth than othercomponent carriers. In time division duplex (TDD) systems, the number ofcomponent carriers as well as the bandwidths of each component carrieris usually the same for DL and UL.

Carrier aggregation can also include individual serving cells to provideindividual component carriers. The coverage of the serving cells maydiffer, for example, because component carriers on different frequencybands may experience different path loss. A primary service cell (PCell)may provide a primary component carrier for both UL and DL, and mayhandle RRC and non-access stratum (NAS) related activities. The otherserving cells are referred to as secondary component carriers (SCells),and each SCell may provide an individual secondary component carrier forboth UL and DL. The secondary component carriers may be added andremoved as required, while changing the primary component carrier mayrequire the UE 101 to undergo a handover. In LAA, eLAA, and feLAA, someor all of the SCells may operate in the unlicensed spectrum (referred toas “LAA SCells”), and the LAA SCells are assisted by a PCell operatingin the licensed spectrum. When a UE is configured with more than one LAASCell, the UE may receive UL grants on the configured LAA SCellsindicating different PUSCH starting positions within a same subframe.

The PDSCH carries user data and higher-layer signaling to the UEs 101.The physical downlink control channel (PDCCH) carries information aboutthe transport format and resource allocations related to the PDSCHchannel, among other things. It may also inform the UEs 101 about thetransport format, resource allocation, and hybrid automatic repeatrequest (HARQ) information related to the uplink shared channel.Downlink scheduling (e.g., assigning control and shared channel resourceblocks to the UE 101 b within a cell) may be performed at any of the RANnodes 111 based on channel quality information fed back from any of theUEs 101. The downlink resource assignment information may be sent on thePDCCH used for (e.g., assigned to) each of the UEs 101.

The PDCCH uses control channel elements (CCEs) to convey the controlinformation. Before being mapped to resource elements, the PDCCHcomplex-valued symbols may first be organized into quadruplets, whichmay then be permuted using a sub-block interleaver for rate matching. Insome examples, each PDCCH may be transmitted using one or more of theseCCEs, in which each CCE may correspond to nine sets of four physicalresource elements collectively referred to as resource element groups(REGs). Four Quadrature Phase Shift Keying (QPSK) symbols may be mappedto each REG. The PDCCH can be transmitted using one or more CCEs,depending on the size of the downlink control information (DCI) and thechannel condition. In LTE, there can be four or more different PDCCHformats defined with different numbers of CCEs (e.g., aggregation level,L=1, 2, 4, or 8).

Some implementations may use concepts for resource allocation forcontrol channel information that are an extension of the above-describedconcepts. For example, some implementations may utilize an enhancedPDCCH (EPDCCH) that uses PDSCH resources for control informationtransmission. The EPDCCH may be transmitted using one or more enhancedCCEs (ECCEs). Similar to above, each ECCE may correspond to nine sets offour physical resource elements collectively referred to as an enhancedREG (EREG). An ECCE may have other numbers of EREGs in some examples.

The RAN nodes 111 are configured to communicate with one another usingan interface 112. In examples, such as where the system 100 is an LTEsystem (e.g., when the core network 120 is an evolved packet core (EPC)network as shown in FIG. 2 ), the interface 112 may be an X2 interface112. The X2 interface may be defined between two or more RAN nodes 111(e.g., two or more eNBs and the like) that connect to the EPC 120, orbetween two eNBs connecting to EPC 120, or both. In some examples, theX2 interface may include an X2 user plane interface (X2-U) and an X2control plane interface (X2-C). The X2-U may provide flow controlmechanisms for user data packets transferred over the X2 interface, andmay be used to communicate information about the delivery of user databetween eNBs. For example, the X2-U may provide specific sequence numberinformation for user data transferred from a master eNB to a secondaryeNB; information about successful in sequence delivery of PDCP protocoldata units (PDUs) to a UE 101 from a secondary eNB for user data;information of PDCP PDUs that were not delivered to a UE 101;information about a current minimum desired buffer size at the secondaryeNB for transmitting to the UE user data, among other information. TheX2-C may provide intra-LTE access mobility functionality, includingcontext transfers from source to target eNBs or user plane transportcontrol; load management functionality; inter-cell interferencecoordination functionality, among other functionality.

In some examples, such as where the system 100 is a 5G NR system (e.g.,when the core network 120 is a 5G core network as shown in FIG. 3 ), theinterface 112 may be an Xn interface 112. The Xn interface may bedefined between two or more RAN nodes 111 (e.g., two or more gNBs andthe like) that connect to the 5G core network 120, between a RAN node111 (e.g., a gNB) connecting to the 5G core network 120 and an eNB, orbetween two eNBs connecting to the 5G core network 120, or combinationsof them. In some examples, the Xn interface may include an Xn user plane(Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U mayprovide non-guaranteed delivery of user plane PDUs and support/providedata forwarding and flow control functionality. The Xn-C may providemanagement and error handling functionality, functionality to manage theXn-C interface; mobility support for UE 101 in a connected mode (e.g.,CM-CONNECTED) including functionality to manage the UE mobility forconnected mode between one or more RAN nodes 111, among otherfunctionality. The mobility support may include context transfer from anold (source) serving RAN node 111 to new (target) serving RAN node 111,and control of user plane tunnels between old (source) serving RAN node111 to new (target) serving RAN node 111. A protocol stack of the Xn-Umay include a transport network layer built on Internet Protocol (IP)transport layer, and a GPRS tunneling protocol for user plane (GTP-U)layer on top of a user datagram protocol (UDP) or IP layer(s), or both,to carry user plane PDUs. The Xn-C protocol stack may include anapplication layer signaling protocol (referred to as Xn ApplicationProtocol (Xn-AP)) and a transport network layer that is built on astream control transmission protocol (SCTP). The SCTP may be on top ofan IP layer, and may provide the guaranteed delivery of applicationlayer messages. In the transport IP layer, point-to-point transmissionis used to deliver the signaling PDUs. In other implementations, theXn-U protocol stack or the Xn-C protocol stack, or both, may be same orsimilar to the user plane and/or control plane protocol stack(s) shownand described herein.

The RAN 110 is shown to be communicatively coupled to a core network 120(referred to as a “CN 120”). The CN 120 includes one or more networkelements 122, which are configured to offer various data andtelecommunications services to customers/subscribers (e.g., users of UEs101) who are connected to the CN 120 using the RAN 110. The componentsof the CN 120 may be implemented in one physical node or separatephysical nodes and may include components to read and executeinstructions from a machine-readable or computer-readable medium (e.g.,a non-transitory machine-readable storage medium). In some examples,network functions virtualization (NFV) may be used to virtualize some orall of the network node functions described here using executableinstructions stored in one or more computer-readable storage mediums, asdescribed in further detail below. A logical instantiation of the CN 120may be referred to as a network slice, and a logical instantiation of aportion of the CN 120 may be referred to as a network sub-slice. NFVarchitectures and infrastructures may be used to virtualize one or morenetwork functions, alternatively performed by proprietary hardware, ontophysical resources comprising a combination of industry-standard serverhardware, storage hardware, or switches. In other words, NFV systems canbe used to execute virtual or reconfigurable implementations of one ormore network components or functions, or both.

Generally, an application server 130 may be an element offeringapplications that use IP bearer resources with the core network (e.g.,UMTS packet services (PS) domain, LTE PS data services, among others).The application server 130 can also be configured to support one or morecommunication services (e.g., VoIP sessions, PTT sessions, groupcommunication sessions, social networking services, among others) forthe UEs 101 using the CN 120.

In some examples, the CN 120 may be a 5G core network (referred to as“5GC 120”), and the RAN 110 may be connected with the CN 120 using anext generation interface 113. In some examples, the next generationinterface 113 may be split into two parts, an next generation user plane(NG-U) interface 114, which carries traffic data between the RAN nodes111 and a user plane function (UPF), and the S1 control plane (NG-C)interface 115, which is a signaling interface between the RAN nodes 111and access and mobility management functions (AMFs). Examples where theCN 120 is a 5GC 120 are discussed in more detail with regard to FIG. 3 .

In some examples, the CN 120 may be an EPC (referred to as “EPC 120” orthe like), and the RAN 110 may be connected with the CN 120 using an S1interface 113. In some examples, the S1 interface 113 may be split intotwo parts, an S1 user plane (S1-U) interface 114, which carries trafficdata between the RAN nodes 111 and the serving gateway (S-GW), and theS1-MME interface 115, which is a signaling interface between the RANnodes 111 and mobility management entities (MMEs).

FIG. 2 illustrates an example architecture of a system 200 including aCN 220. In this example, the system 200 may implement the LTE standardsuch that the CN 220 is an EPC 220 that corresponds with CN 120 of FIG.1 . Additionally, the UE 201 may be the same or similar as the UEs 101of FIG. 1 , and the E-UTRAN 210 may be a RAN that is the same or similarto the RAN 110 of FIG. 1 , and which may include RAN nodes 111 discussedpreviously. The CN 220 may comprise MMEs 221, an S-GW 222, a PDN gateway(P-GW) 223, a high-speed packet access (HSS) function 224, and a servingGPRS support node (SGSN) 225.

The MMEs 221 may be similar in function to the control plane of legacySGSN, and may implement mobility management (MM) functions to keep trackof the current location of a UE 201. The MMEs 221 may perform variousmobility management procedures to manage mobility aspects in access suchas gateway selection and tracking area list management. Mobilitymanagement (also referred to as “EPS MM” or “EMM” in E-UTRAN systems)may refer to all applicable procedures, methods, data storage, and otheraspects that are used to maintain knowledge about a present location ofthe UE 201, provide user identity confidentiality, or perform other likeservices to users/subscribers, or combinations of them, among others.Each UE 201 and the MME 221 may include an EMM sublayer, and an mobilitymanagement context may be established in the UE 201 and the MME 221 whenan attach procedure is successfully completed. The mobility managementcontext may be a data structure or database object that stores mobilitymanagement-related information of the UE 201. The MMEs 221 may becoupled with the HSS 224 using a S6a reference point, coupled with theSGSN 225 using a S3 reference point, and coupled with the S-GW 222 usinga S11 reference point.

The SGSN 225 may be a node that serves the UE 201 by tracking thelocation of an individual UE 201 and performing security functions. Inaddition, the SGSN 225 may perform Inter-EPC node signaling for mobilitybetween 2G/3G and E-UTRAN 3GPP access networks; PDN and S-GW selectionas specified by the MMEs 221; handling of UE 201 time zone functions asspecified by the MMEs 221; and MME selection for handovers to E-UTRAN3GPP access network, among other functions. The S3 reference pointbetween the MMEs 221 and the SGSN 225 may enable user and bearerinformation exchange for inter-3GPP access network mobility in idle oractive states, or both.

The HSS 224 may include a database for network users, includingsubscription-related information to support the network entities'handling of communication sessions. The EPC 220 may include one or moreHSSs 224 depending on the number of mobile subscribers, on the capacityof the equipment, on the organization of the network, or combinations ofthem, among other features. For example, the HSS 224 can provide supportfor routing, roaming, authentication, authorization, naming/addressingresolution, location dependencies, among others. A S6a reference pointbetween the HSS 224 and the MMEs 221 may enable transfer of subscriptionand authentication data for authenticating or authorizing user access tothe EPC 220 between HSS 224 and the MMEs 221.

The S-GW 222 may terminate the S1 interface 113 (“S1-U” in FIG. 2 )toward the RAN 210, and may route data packets between the RAN 210 andthe EPC 220. In addition, the S-GW 222 may be a local mobility anchorpoint for inter-RAN node handovers and also may provide an anchor forinter-3GPP mobility. Other responsibilities may include lawfulintercept, charging, and some policy enforcement. The S11 referencepoint between the S-GW 222 and the MMEs 221 may provide a control planebetween the MMEs 221 and the S-GW 222. The S-GW 222 may be coupled withthe P-GW 223 using a S5 reference point.

The P-GW 223 may terminate a SGi interface toward a PDN 230. The P-GW223 may route data packets between the EPC 220 and external networkssuch as a network including the application server 130 (sometimesreferred to as an “AF”) using an IP interface 125 (see, e.g., FIG. 1 ).In some examples, the P-GW 223 may be communicatively coupled to anapplication server (e.g., the application server 130 of FIG. 1 or PDN230 in FIG. 2 ) using an IP communications interface 125 (see, e.g.,FIG. 1 ). The S5 reference point between the P-GW 223 and the S-GW 222may provide user plane tunneling and tunnel management between the P-GW223 and the S-GW 222. The S5 reference point may also be used for S-GW222 relocation due to UE 201 mobility and if the S-GW 222 needs toconnect to a non-collocated P-GW 223 for the required PDN connectivity.The P-GW 223 may further include a node for policy enforcement andcharging data collection (e.g., PCEF (not shown)). Additionally, the SGireference point between the P-GW 223 and the packet data network (PDN)230 may be an operator external public, a private PDN, or an intraoperator packet data network, for example, for provision of IMSservices. The P-GW 223 may be coupled with a policy control and chargingrules function (PCRF) 226 using a Gx reference point.

PCRF 226 is the policy and charging control element of the EPC 220. In anon-roaming scenario, there may be a single PCRF 226 in the Home PublicLand Mobile Network (HPLMN) associated with a UE 201's Internet ProtocolConnectivity Access Network (IP-CAN) session. In a roaming scenario withlocal breakout of traffic, there may be two PCRFs associated with a UE201's IP-CAN session, a Home PCRF (H-PCRF) within an HPLMN and a VisitedPCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). ThePCRF 226 may be communicatively coupled to the application server 230using the P-GW 223. The application server 230 may signal the PCRF 226to indicate a new service flow and select the appropriate quality ofservice (QoS) and charging parameters. The PCRF 226 may provision thisrule into a PCEF (not shown) with the appropriate traffic flow template(TFT) and QoS class identifier (QCI), which commences the QoS andcharging as specified by the application server 230. The Gx referencepoint between the PCRF 226 and the P-GW 223 may allow for the transferof QoS policy and charging rules from the PCRF 226 to PCEF in the P-GW223. A Rx reference point may reside between the PDN 230 (or “AF 230”)and the PCRF 226.

FIG. 3 illustrates an architecture of a system 300 including a CN 320.The system 300 is shown to include a UE 301, which may be the same orsimilar to the UEs 101 and UE 201 discussed previously; a (R)AN 310,which may be the same or similar to the RAN 110 and RAN 210 discussedpreviously, and which may include RAN nodes 111 discussed previously;and a data network (DN) 303, which may be, for example, operatorservices, Internet access or 3rd party services; and a 5GC 320. The 5GC320 may include an authentication server function (AUSF) 322; an accessand mobility management function (AMF) 321; a session managementfunction (SMF) 324; a network exposure function (NEF) 323; a policycontrol function (PCF) 326; a network repository function (NRF) 325; aunified data management (UDM) function 327; an AF 328; a user planefunction (UPF) 302; and a network slice selection function (NSSF) 329.

The UPF 302 may act as an anchor point for intra-RAT and inter-RATmobility, an external PDU session point of interconnect to DN 303, and abranching point to support multi-homed PDU session. The UPF 302 may alsoperform packet routing and forwarding, perform packet inspection,enforce the user plane part of policy rules, lawfully intercept packets(UP collection), perform traffic usage reporting, perform QoS handlingfor a user plane (e.g., packet filtering, gating, ULDL rateenforcement), perform Uplink Traffic verification (e.g., SDF to QoS flowmapping), transport level packet marking in the uplink and downlink, andperform downlink packet buffering and downlink data notificationtriggering. UPF 302 may include an uplink classifier to support routingtraffic flows to a data network. The DN 303 may represent variousnetwork operator services, Internet access, or third party services. DN303 may include, or be similar to, application server 130 discussedpreviously. The UPF 302 may interact with the SMF 324 using a N4reference point between the SMF 324 and the UPF 302.

In some examples, the UPF 302 supports Performance MeasurementFunctionality (PMF), which may be used by the UE 301 to obtain accessperformance measurements over the user-plane of 3GPP access and/or overthe user-plane of non-3GPP access. For example, when the UE 301 requestsestablishment of a Multiple Access Protocol Data Unit (MA PDU) Sessionand indicates that it is capable of supporting Access Traffic Steering,Switching and Splitting (ATSSS), the UE may receive MeasurementAssistance Information during the establishment of a MA PDU session.This information assists the UE in determining which measurements shouldbe performed over either or both accesses, as well as whether and whenmeasurement reports should to be sent to the network. MeasurementAssistance Information can include, for example, the IP address and theUDP port of a PMF in the UPF 302, with which the UE 301 can send PMFprotocol messages. Additional details on access network performancemeasurements are described in clause 5.32.5 of 3GPP TechnicalSpecification (TS) 23.501, the entire content of which is incorporatedherein by reference.

In some examples, the following PMF protocol messages can be exchangedbetween the UE and the PMF: Messages for Round Trip Time (RTT)measurements (e.g., when the “Smallest Delay” steering mode is used);and messages for reporting access availability/unavailability by the UE301 to the UPF 302. In some examples, such as when the UE requests a MAPDU session and indicates that it is capable of supporting the MultipathTCP (MPTCP) functionality only, the network may not send MeasurementAssistance Information, as the UE can use measurements available at theMPTCP layer.

The AUSF 322 stores data for authentication of UE 301 and handleauthentication-related functionality. The AUSF 322 may facilitate acommon authentication framework for various access types. The AUSF 322may communicate with the AMF 321 using a N12 reference point between theAMF 321 and the AUSF 322, and may communicate with the UDM 327 using aN13 reference point between the UDM 327 and the AUSF 322. Additionally,the AUSF 322 may exhibit a Nausf service-based interface.

The AMF 321 is responsible for registration management (e.g., forregistering UE 301), connection management, reachability management,mobility management, and lawful interception of AMF-related events, andaccess authentication and authorization. The AMF 321 may be atermination point for the N11 reference point between the AMF 321 andthe SMF 324. The AMF 321 may provide transport for SM messages betweenthe UE 301 and the SMF 324, and act as a transparent proxy for routingSM messages. AMF 321 may also provide transport for short messageservice (SMS) messages between UE 301 and a SMS Function (SMSF) (notshown in FIG. 3 ). AMF 321 may act as security anchor function (SEAF),which may include interaction with the AUSF 322 and the UE 301 to, forexample, receive an intermediate key that was established as a result ofthe UE 301 authentication process. Where universal subscriber identitymodule (USIM) based authentication is used, the AMF 321 may retrieve thesecurity material from the AUSF 322. AMF 321 may also include a securitycontext management (SCM) function, which receives a key from the SEAF toderive access-network specific keys. Furthermore, AMF 321 may be atermination point of a RAN control plane interface, which may include orbe a N2 reference point between the (R)AN 310 and the AMF 321. In someexamples, the AMF 321 may be a termination point of NAS (N1) signalingand perform NAS ciphering and integrity protection.

AMF 321 may also support NAS signaling with a UE 301 over a N3interworking function (IWF) interface (referred to as the “N31WF”). TheN3IWF may be used to provide access to untrusted entities. The N3IWF maybe a termination point for the N2 interface between the (R)AN 310 andthe AMF 321 for the control plane, and may be a termination point forthe N3 reference point between the (R)AN 310 and the UPF 302 for theuser plane. As such, the AMF 321 may handle N2 signaling from the SMF324 and the AMF 321 for PDU sessions and QoS, encapsulate/de-encapsulatepackets for IPsec and N3 tunneling, mark N3 user-plane packets in theuplink, and enforce QoS corresponding to N3 packet marking taking intoaccount QoS requirements associated with such marking received over N2.The N3IWF may also relay uplink and downlink control-plane NAS signalingbetween the UE 301 and AMF 321 using a N1 reference point between the UE301 and the AMF 321, and relay uplink and downlink user-plane packetsbetween the UE 301 and UPF 302. The N3IWF also provides mechanisms forIPsec tunnel establishment with the UE 301. The AMF 321 may exhibit aNamf service-based interface, and may be a termination point for a N14reference point between two AMFs 321 and a N17 reference point betweenthe AMF 321 and a 5G equipment identity registry (EIR) (not shown inFIG. 3 ).

The UE 301 may register with the AMF 321 in order to receive networkservices. Registration management (RM) is used to register or deregisterthe UE 301 with the network (e.g., AMF 321), and establish a UE contextin the network (e.g., AMF 321). The UE 301 may operate in aRM-REGISTERED state or an RM-DEREGISTERED state. In the RM DEREGISTEREDstate, the UE 301 is not registered with the network, and the UE contextin AMF 321 holds no valid location or routing information for the UE 301so the UE 301 is not reachable by the AMF 321. In the RM REGISTEREDstate, the UE 301 is registered with the network, and the UE context inAMF 321 may hold a valid location or routing information for the UE 301so the UE 301 is reachable by the AMF 321. In the RM-REGISTERED state,the UE 301 may perform mobility Registration Update procedures, performperiodic Registration Update procedures triggered by expiration of theperiodic update timer (e.g., to notify the network that the UE 301 isstill active), and perform a Registration Update procedure to update UEcapability information or to re-negotiate protocol parameters with thenetwork, among others.

The AMF 321 may store one or more RM contexts for the UE 301, where eachRM context is associated with a specific access to the network. The RMcontext may be, for example, a data structure or database object, amongothers, that indicates or stores a registration state per access typeand the periodic update timer. The AMF 321 may also store a 5GC mobilitymanagement (MM) context that may be the same or similar to the (E)MMcontext discussed previously. In some examples, the AMF 321 may store acoverage enhancement mode B Restriction parameter of the UE 301 in anassociated MM context or RM context. The AMF 321 may also derive thevalue, when needed, from the UE's usage setting parameter already storedin the UE context (and/or MM/RM context).

Connection management (CM) may be used to establish and release asignaling connection between the UE 301 and the AMF 321 over the N1interface. The signaling connection is used to enable NAS signalingexchange between the UE 301 and the CN 320, and includes both thesignaling connection between the UE and the AN (e.g., RRC connection orUE-N3IWF connection for non-3GPP access) and the N2 connection for theUE 301 between the AN (e.g., RAN 310) and the AMF 321. In some examples,the UE 301 may operate in one of two CM modes: CM-IDLE mode orCM-CONNECTED mode. When the UE 301 is operating in the CM-IDLE mode, theUE 301 may have no NAS signaling connection established with the AMF 321over the N1 interface, and there may be (R)AN 310 signaling connection(e.g., N2 or N3 connections, or both) for the UE 301. When the UE 301 isoperating in the CM-CONNECTED mode, the UE 301 may have an establishedNAS signaling connection with the AMF 321 over the N1 interface, andthere may be a (R)AN 310 signaling connection (e.g., N2 and/or N3connections) for the UE 301. Establishment of a N2 connection betweenthe (R)AN 310 and the AMF 321 may cause the UE 301 to transition fromthe CM-IDLE mode to the CM-CONNECTED mode, and the UE 301 may transitionfrom the CM-CONNECTED mode to the CM-IDLE mode when N2 signaling betweenthe (R)AN 310 and the AMF 321 is released.

The SMF 324 may be responsible for session management (SM), such assession establishment, modify and release, including tunnel maintainbetween UPF and AN node; UE IP address allocation and management(including optional authorization); selection and control of UPfunction; configuring traffic steering at the UPF to route traffic toproper destination; termination of interfaces toward policy controlfunctions; controlling part of policy enforcement and QoS; lawfulintercept (for SM events and interface to LI system); termination of SMparts of NAS messages; downlink data notification; initiating ANspecific SM information, sent using AMF over N2 to AN; and determiningSSC mode of a session. SM may refer to management of a PDU session, anda PDU session (or “session”) may refer to a PDU connectivity servicethat provides or enables the exchange of PDUs between a UE 301 and adata network (DN) 303 identified by a Data Network Name (DNN). PDUsessions may be established upon UE 301 request, modified upon UE 301and 5GC 320 request, and released upon UE 301 and 5GC 320 request usingNAS SM signaling exchanged over the N1 reference point between the UE301 and the SMF 324. Upon request from an application server, the 5GC320 may trigger a specific application in the UE 301. In response toreceipt of the trigger message, the UE 301 may pass the trigger message(or relevant parts/information of the trigger message) to one or moreidentified applications in the UE 301. The identified application(s) inthe UE 301 may establish a PDU session to a specific DNN. The SMF 324may check whether the UE 301 requests are compliant with usersubscription information associated with the UE 301. In this regard, theSMF 324 may retrieve and/or request to receive update notifications onSMF 324 level subscription data from the UDM 327.

The SMF 324 may include some or all of the following roamingfunctionality: handling local enforcement to apply QoS service levelagreements (SLAs) (e.g., in VPLMN); charging data collection andcharging interface (e.g., in VPLMN); lawful intercept (e.g., in VPLMNfor SM events and interface to LI system); and support for interactionwith external DN for transport of signaling for PDU sessionauthorization/authentication by external DN. A N16 reference pointbetween two SMFs 324 may be included in the system 300, which may bebetween another SMF 324 in a visited network and the SMF 324 in the homenetwork in roaming scenarios. Additionally, the SMF 324 may exhibit theNsmf service-based interface.

The NEF 323 may provide means for securely exposing the services andcapabilities provided by 3GPP network functions for third party,internal exposure/re-exposure, Application Functions (e.g., AF 328),edge computing or fog computing systems, among others. In some examples,the NEF 323 stores/retrieves information as structured data using astandardized interface (Nudr) to the Unified Data Repository (UDR), andthe NEF 323 may authenticate, authorize, and/or throttle the AFs.

The NEF 323 may also translate information exchanged with the AF 328 andinformation exchanged with internal network functions. For example, theNEF 323 may translate between an AF-Service-Identifier and an internal5GC information. The NEF 323 may also receive information from othernetwork functions (NFs) based on exposed capabilities of other NFs. Thisinformation may be stored at the NEF 323 as structured data, or at adata storage NF using standardized interfaces. The stored informationcan then be re-exposed by the NEF 323 to other NFs and AFs, or used forother purposes such as analytics, or both. Additionally, the NEF 323 mayexhibit a Nnef service-based interface.

In particular, in some examples, the NEF 323 handles masking of networkand user sensitive information to external AFs (e.g., AFs 328) accordingto a network policy. The NEF 323 may also support a Packet FlowDescription (PFD) Function, which may store and retrieve PFD(s) in theUDR and provides PFD(s) to the SMF 324 on the request of the SMF 324(sometimes referred to as “pull mode”), or on the request of PFDmanagement from the NEF 328 (sometimes referred to as “push mode”), asdescribed in 3GPP TS 23.503, the entire content of which is incorporatedherein by reference.

In some examples, the NEF 323 provides a means for the AF 328 tosecurely provide information to a 3GPP network (e.g., Expected UEBehavior, 5GLAN group information, or service specific information, orcombinations of them, among other information). In this example, the NEFmay authenticate and authorize and assist in throttling the AFs 328.

In some examples, the NEF 323 may provide one or a combination of two ormore of the functions or services summarized below in Table 1 anddescribed in 3GPP TS 23.502, the entire content of which is incorporatedherein by reference.

TABLE 1 Example NE Services provided by NEF Service Name DescriptionClause in 3GPP TS 23.502 Nnef_EventExposure Provides support for eventexposure 5.2.6.2  Nnef_PFDManagement Provides support for PEDs 5.2.6.3 management Nnef_ParameterProvision Provides support to provision5.2.6.4  information which can be used for the UE in 5GS Nnef_TriggerProvides support for device 5.2.6.5  triggering Nnef_BDTPNegotiationProvides support for background 5.2.6.6  data transfer policynegotiation and optionally notification for the renegotiation.Nnef_TrafficInfluence Provide the ability to influence 5.2.6.7  trafficrouting. Nnef_ChargeableParty Requests to become the chargeable 5.2.6.8 party for a data session for UE. Nnef_AFsessionWithQoS Requests thenetwork to provide a 5.2.6.9  specific QoS for an AS session.Nnef_ServiceParameter Provides support to provision 5.2.6.11 servicespecific information Nnef_APISupportCapability Provides support forawareness on 5.2.6.12 availability or expected level of a service APINnef_AnalyticsExposure Provides support for exposure of 5.2.6.16 networkanalytics

The NRF 325 may support service discovery functions, receive NFdiscovery requests from NF instances, and provide the information of thediscovered NF instances to the NF instances. NRF 325 also maintainsinformation of available NF instances and their supported services. Asused herein, the terms “instantiate,” “instantiation,” and the like mayrefer to the creation of an instance, and an “instance” may refer to aconcrete occurrence of an object, which may occur, for example, duringexecution of program code. Additionally, the NRF 325 may exhibit theNnrf service-based interface.

In general, NFs may offer different capabilities, and thus different NFservices to distinct consumers. An NF service is one type of capabilityexposed by a NF (e.g., a NF Service Producer) to another authorized NF(e.g., a NF Service Consumer) through a service-based interface. A NFmay expose one or more NF services. Each of the NF services offered by aNF are self-contained, reusable, and use management schemesindependently of other NF services offered by the same NF (e.g., forscaling, healing, etc.). A consumer having selected a NF serviceinstance within a NF instance may re-select another service instance ofthe same NF service within that same NF instance and get the sameresults as if the original selected NF service instance was used.Re-selecting may be needed if the service consumer fails to contact theoriginal NF service instance.

In some examples, each NF service is accessible by means of aninterface. An interface comprises one or several operations. NF servicesmay communicate directly between NF Service Consumers and NF ServiceProducers, or indirectly via a Service Communication Proxy (SCP).Whether a NF Service Consumer uses direct or indirect communication canbe based on the configuration of the NF Service Consumer. In directcommunication, the NF Service Consumer performs discovery of the targetNF Service producer by local configuration or via NRF. Then, the NFService Consumer communicates with the target NF Service Producerdirectly. In indirect communication, the NF Service Consumercommunicates with the target NF Service producer via a SCP. The NFService Consumer may be configured to perform discovery of the target NFService Producer directly, or delegate the discovery of the target NFService Producer to the SCP used for indirect communication. In thelatter case, the SCP uses the parameters provided by NF Service Consumerto perform discovery and/or selection of the target NF Service Producer.The SCP address may be locally configured in or by the NF ServiceConsumer.

In some examples, if the end point address provided by a NF ServiceProducer points to a specific target NF Producer/NF Service Producerinstance within a set, the NF Consumer or SCP may re-select anotherservice instance of the same NF service within the same NF service setin that same NF instance, or another NF instance in the same NF Set forsubsequent transaction, and get the same results as if the originalselected NF service instance was used. Re-selecting may be used, forexample, if the requester NF fails to contact the original NF serviceinstance. If the end point address provided by the NF Service Producerpoints to an NF set or NF service set, the NF Consumer or SCP is allowedto reselect a different NF service instance of the same NF servicewithin that same set for the UE and its subsequent transaction. Systemprocedures can be built by invocation of a number of NF services (e.g.,as specified in 3GPP TS 23.502).

The PCF 326 may provide policy rules to control plane function(s) toenforce them, and may also support unified policy framework to governnetwork behavior. The PCF 326 may also implement a front end to accesssubscription information relevant for policy decisions in a unified datarepository (UDR) of the UDM 327. The PCF 326 may communicate with theAMF 321 using an N15 reference point between the PCF 326 and the AMF321, which may include a PCF 326 in a visited network and the AMF 321 incase of roaming scenarios. The PCF 326 may communicate with the AF 328using a N5 reference point between the PCF 326 and the AF 328; and withthe SMF 324 using a N7 reference point between the PCF 326 and the SMF324. The system 300 or CN 320, or both, may also include a N24 referencepoint between the PCF 326 (in the home network) and a PCF 326 in avisited network. Additionally, the PCF 326 may exhibit a Npcfservice-based interface.

The UDM 327 may handle subscription-related information to support thenetwork entities' handling of communication sessions, and may storesubscription data of UE 301. For example, subscription data may becommunicated between the UDM 327 and the AMF 321 using a N8 referencepoint between the UDM 327 and the AMF. The UDM 327 may include twoparts, an application front end and a UDR (the front end and UDR are notshown in FIG. 3 ). The UDR may store subscription data and policy datafor the UDM 327 and the PCF 326, or structured data for exposure andapplication data (including PFDs for application detection, applicationrequest information for multiple UEs 301) for the NEF 323, or both. TheNudr service-based interface may be exhibited by the UDR 221 to allowthe UDM 327, PCF 326, and NEF 323 to access a particular set of thestored data, as well as to read, update (e.g., add, modify), delete, andsubscribe to notification of relevant data changes in the UDR. The UDMmay include a UDM front end, which is in charge of processingcredentials, location management, subscription management and so on.Several different front ends may serve the same user in differenttransactions. The UDM front end accesses subscription information storedin the UDR and performs authentication credential processing, useridentification handling, access authorization, registration/mobilitymanagement, and subscription management. The UDR may interact with theSMF 324 using a N10 reference point between the UDM 327 and the SMF 324.UDM 327 may also support SMS management, in which an SMS front endimplements the similar application logic as discussed previously.Additionally, the UDM 327 may exhibit the Nudm service-based interface.

The AF 328 may provide application influence on traffic routing, provideaccess to the network capability exposure (NCE), and interact with thepolicy framework for policy control. The NCE may be a mechanism thatallows the 5GC 320 and AF 328 to provide information to each other usingNEF 323, which may be used for edge computing implementations. In suchimplementations, the network operator and third party services may behosted close to the UE 301 access point of attachment to achieve anefficient service delivery through the reduced end-to-end latency andload on the transport network. For edge computing implementations, the5GC may select a UPF 302 close to the UE 301 and execute trafficsteering from the UPF 302 to DN 303 using the N6 interface. This may bebased on the UE subscription data, UE location, and information providedby the AF 328. In this way, the AF 328 may influence UPF (re)selectionand traffic routing. Based on operator deployment, when AF 328 isconsidered to be a trusted entity, the network operator may permit AF328 to interact directly with relevant NFs. Additionally, the AF 328 mayexhibit a Naf service-based interface.

The NSSF 329 may select a set of network slice instances serving the UE301. The NSSF 329 may also determine allowed NSSAI and the mapping tothe subscribed single network slice selection assistance information(S-NSSAI), if needed. The NSSF 329 may also determine the AMF set to beused to serve the UE 301, or a list of candidate AMF(s) 321 based on asuitable configuration and possibly by querying the NRF 325. Theselection of a set of network slice instances for the UE 301 may betriggered by the AMF 321 with which the UE 301 is registered byinteracting with the NSSF 329, which may lead to a change of AMF 321.The NSSF 329 may interact with the AMF 321 using an N22 reference pointbetween AMF 321 and NSSF 329; and may communicate with another NSSF 329in a visited network using a N31 reference point (not shown by FIG. 3 ).Additionally, the NSSF 329 may exhibit a Nnssf service-based interface.

As discussed previously, the CN 320 may include an SMSF, which may beresponsible for SMS subscription checking and verification, and relayingSM messages to or from the UE 301 to or from other entities, such as anSMS-GMSC/IWMSC/SMS-router. The SMS may also interact with AMF 321 andUDM 327 for a notification procedure that the UE 301 is available forSMS transfer (e.g., set a UE not reachable flag, and notifying UDM 327when UE 301 is available for SMS).

The CN 120 may also include other elements that are not shown in FIG. 3, such as a data storage system, a 5G-EIR, a security edge protectionproxy (SEPP), and the like. The data storage system may include astructured data storage function (SDSF), an unstructured data storagefunction (UDSF), or both, among others. Any network function may storeand retrieve unstructured data to or from the UDSF (e.g., UE contexts),using a N18 reference point between any NF and the UDSF (not shown inFIG. 3 ). Individual network functions may share a UDSF for storingtheir respective unstructured data or individual network functions mayeach have their own UDSF located at or near the individual networkfunctions. Additionally, the UDSF may exhibit a Nudsf service-basedinterface (not shown in FIG. 3 ). The 5G-EIR may be a network functionthat checks the status of permanent equipment identifiers (PEI) fordetermining whether particular equipment or entities are blacklistedfrom the network.

The SEPP may be a non-transparent proxy that performs topology hiding,message filtering, and policing on inter-PLMN control plane interfaces.The SEPP protects the connection between Service Consumers and ServiceProducers from a security perspective. For example, the SEPP does notduplicate the Service Authorization applied by the Service Producers asspecified in clause 7.1.4 of 3GPP TS 23.501. Detailed functionality ofthe SEPP, related flows, and the N32 reference point, are specified in3GPP TS 33.501. In some examples, the SEPP applies the aforementionedfunctionality to each Control Plane message in inter-PLMN signaling,acting as a service relay between the actual Service Producer and theactual Service Consumer. For both Service Producer and Consumer, theresult of the service relaying is equivalent to a direct serviceinteraction. Every Control Plane message in inter-PLMN signaling betweenthe SEPPs may pass via IPX entities. More details on SEPPs and the IPXentities are described in 3GPP TS 33.501 and TS 29.500, the entirecontents of each of which is incorporated herein by reference.

In some examples, there may be additional or alternative referencepoints or service-based interfaces, or both, between the networkfunction services in the network functions. However, these interfacesand reference points have been omitted from FIG. 3 for clarity. In oneexample, the CN 320 may include a Nx interface, which is an inter-CNinterface between the MME (e.g., MME 221) and the AMF 321 in order toenable interworking between CN 320 and CN 220. Other example interfacesor reference points may include a N5g-EIR service-based interfaceexhibited by a 5G-EIR, a N27 reference point between the NRF in thevisited network and the NRF in the home network, or a N31 referencepoint between the NSSF in the visited network and the NSSF in the homenetwork, among others.

FIG. 4 illustrates an example of infrastructure equipment 400. Theinfrastructure equipment 400 (or “system 400”) may be implemented as abase station, a radio head, a RAN node, such as the RAN nodes 111 or AP106 shown and described previously, an application server(s) 130, or anyother component or device described herein. In other examples, thesystem 400 can be implemented in or by a UE.

The system 400 includes application circuitry 405, baseband circuitry410, one or more radio front end modules (RFEMs) 415, memory circuitry420, power management integrated circuitry (PMIC) 425, power teecircuitry 430, network controller circuitry 435, network interfaceconnector 440, satellite positioning circuitry 445, and user interfacecircuitry 450. In some examples, the system 400 may include additionalelements such as, for example, memory, storage, a display, a camera, oneor more sensors, or an input/output (I/O) interface, or combinations ofthem, among others. In other examples, the components described withreference to the system 400 may be included in more than one device. Forexample, the various circuitries may be separately included in more thanone device for CRAN, vBBU, or other implementations.

The application circuitry 405 includes circuitry such as, but notlimited to, one or more processors (or processor cores), cache memory,one or more of low drop-out voltage regulators (LDOs), interruptcontrollers, serial interfaces such as SPI, I2C or universalprogrammable serial interface module, real time clock (RTC),timer-counters including interval and watchdog timers, general purposeinput/output (I/O or IO), memory card controllers such as Secure Digital(SD) MultiMediaCard (MMC) or similar, Universal Serial Bus (USB)interfaces, Mobile Industry Processor Interface (MIPI) interfaces andJoint Test Access Group (JTAG) test access ports. The processors (orcores) of the application circuitry 405 may be coupled with or mayinclude memory or storage elements and may be configured to executeinstructions stored in the memory or storage to enable variousapplications or operating systems to run on the system 400. In someexamples, the memory or storage elements may include on-chip memorycircuitry, which may include any suitable volatile or non-volatilememory, such as DRAM, SRAM, EPROM, EEPROM, Flash memory, solid-statememory, or combinations of them, among other types of memory.

The processor(s) of the application circuitry 405 may include, forexample, one or more processor cores (CPUs), one or more applicationprocessors, one or more graphics processing units (GPUs), one or morereduced instruction set computing (RISC) processors, one or more AcornRISC Machine (ARM) processors, one or more complex instruction setcomputing (CISC) processors, one or more digital signal processors(DSP), one or more FPGAs, one or more PLDs, one or more ASICs, one ormore microprocessors or controllers, or combinations of them, amongothers. In some examples, the application circuitry 405 may include, ormay be, a special-purpose processor or controller configured to carryout the various techniques described here. As examples, the processor(s)of application circuitry 405 may include one or more Apple A-seriesprocessors, Intel Pentium®, Core®, or Xeon® processor(s): Advanced MicroDevices (AMD) Ryzen® processor(s), Accelerated Processing Units (APUs),or Epyc® processors; ARM-based processor(s) licensed from ARM Holdings,Ltd. such as the ARM Cortex-A family of processors and the ThunderX2®provided by Cavium™, Inc.; a MIPS-based design from MIPS Technologies,Inc. such as MIPS Warrior P-class processors; and/or the like. In someexamples, the system 400 may not utilize application circuitry 405, andinstead may include a special-purpose processor or controller to processIP data received from an EPC or 5GC, for example.

In some examples, the application circuitry 405 may include one or morehardware accelerators, which may be microprocessors, programmableprocessing devices, or the like. The one or more hardware acceleratorsmay include, for example, computer vision (CV) or deep learning (DL)accelerators, or both. In some examples, the programmable processingdevices may be one or more a field-programmable devices (FPDs) such asfield-programmable gate arrays (FPGAs) and the like; programmable logicdevices (PLDs) such as complex PLDs (CPLDs) or high-capacity PLDs(HCPLDs); ASICs such as structured ASICs; programmable SoCs (PSoCs), orcombinations of them, among others. In such implementations, thecircuitry of application circuitry 405 may include logic blocks or logicfabric, and other interconnected resources that may be programmed toperform various functions, such as the procedures, methods, functionsdescribed herein. In some examples, the circuitry of applicationcircuitry 405 may include memory cells (e.g., erasable programmableread-only memory (EPROM), electrically erasable programmable read-onlymemory (EEPROM), flash memory, static memory (e.g., static random accessmemory (SRAM) or anti-fuses)) used to store logic blocks, logic fabric,data, or other data in look-up-tables (LUTs) and the like.

The baseband circuitry 410 may be implemented, for example, as asolder-down substrate including one or more integrated circuits, asingle packaged integrated circuit soldered to a main circuit board or amulti-chip module containing two or more integrated circuits. Thevarious hardware electronic elements of baseband circuitry 410 arediscussed with regard to FIG. 6 .

The user interface circuitry 450 may include one or more user interfacesdesigned to enable user interaction with the system 400 or peripheralcomponent interfaces designed to enable peripheral component interactionwith the system 400. User interfaces may include, but are not limitedto, one or more physical or virtual buttons (e.g., a reset button), oneor more indicators (e.g., light emitting diodes (LEDs)), a physicalkeyboard or keypad, a mouse, a touchpad, a touchscreen, speakers orother audio emitting devices, microphones, a printer, a scanner, aheadset, a display screen or display device, or combinations of them,among others. Peripheral component interfaces may include, but are notlimited to, a nonvolatile memory port, a universal serial bus (USB)port, an audio jack, a power supply interface, among others.

The radio front end modules (RFEMs) 415 may include a millimeter wave(mmWave) RFEM and one or more sub-mmWave radio frequency integratedcircuits (RFICs). In some examples, the one or more sub-mmWave RFICs maybe physically separated from the mmWave RFEM. The RFICs may includeconnections to one or more antennas or antenna arrays (see, e.g.,antenna array 611 of FIG. 6 ), and the RFEM may be connected to multipleantennas. In some examples, both mmWave and sub-mmWave radio functionsmay be implemented in the same physical RFEM 415, which incorporatesboth mmWave antennas and sub-mmWave.

The memory circuitry 420 may include one or more of volatile memory,such as dynamic random access memory (DRAM) or synchronous dynamicrandom access memory (SDRAM), and nonvolatile memory (NVM), such ashigh-speed electrically erasable memory (commonly referred to as Flashmemory), phase change random access memory (PRAM), or magnetoresistiverandom access memory (MRAM), or combinations of them, among others. Insome examples, the memory circuitry 420 may include three-dimensional(3D) cross-point (XPOINT) memories from Intel® and Micron®. Memorycircuitry 420 may be implemented as one or more of solder down packagedintegrated circuits, socketed memory modules and plug-in memory cards,for example.

The PMIC 425 may include voltage regulators, surge protectors, poweralarm detection circuitry, and one or more backup power sources such asa battery or capacitor. The power alarm detection circuitry may detectone or more of brown out (under-voltage) and surge (over-voltage)conditions. The power tee circuitry 430 may provide for electrical powerdrawn from a network cable to provide both power supply and dataconnectivity to the infrastructure equipment 400 using a single cable.

The network controller circuitry 435 may provide connectivity to anetwork using a standard network interface protocol such as Ethernet,Ethernet over GRE Tunnels, Ethernet over Multiprotocol Label Switching(MPLS), or some other suitable protocol. Network connectivity may beprovided to and from the infrastructure equipment 400 using networkinterface connector 440 using a physical connection, which may beelectrical (commonly referred to as a “copper interconnect”), optical,or wireless. The network controller circuitry 435 may include one ormore dedicated processors or FPGAs, or both, to communicate using one ormore of the aforementioned protocols. In some examples, the networkcontroller circuitry 435 may include multiple controllers to provideconnectivity to other networks using the same or different protocols.

The positioning circuitry 445 includes circuitry to receive and decodesignals transmitted or broadcasted by a positioning network of a globalnavigation satellite system (GNSS). Examples of a GNSS include UnitedStates' Global Positioning System (GPS), Russia's Global NavigationSystem (GLONASS), the European Union's Galileo system, China's BeiDouNavigation Satellite System, a regional navigation system or GNSSaugmentation system (e.g., Navigation with Indian Constellation (NAVIC),Japan's Quasi-Zenith Satellite System (QZSS), France's DopplerOrbitography and Radio-positioning Integrated by Satellite (DORIS)),among other systems. The positioning circuitry 445 can include varioushardware elements (e.g., including hardware devices such as switches,filters, amplifiers, antenna elements, and the like to facilitate OTAcommunications) to communicate with components of a positioning network,such as navigation satellite constellation nodes. In some examples, thepositioning circuitry 445 may include a Micro-Technology forPositioning, Navigation, and Timing (Micro-PNT) IC that uses a mastertiming clock to perform position tracking and estimation without GNSSassistance. The positioning circuitry 445 may also be part of, orinteract with, the baseband circuitry 410 or RFEMs 415, or both, tocommunicate with the nodes and components of the positioning network.The positioning circuitry 445 may also provide data (e.g., positiondata, time data) to the application circuitry 405, which may use thedata to synchronize operations with various infrastructure (e.g., RANnodes 111).

The components shown by FIG. 4 may communicate with one another usinginterface circuitry, which may include any number of bus or interconnect(IX) technologies such as industry standard architecture (ISA), extendedISA (EISA), peripheral component interconnect (PCI), peripheralcomponent interconnect extended (PCIx), PCI express (PCIe), or anynumber of other technologies. The bus or IX may be a proprietary bus,for example, used in a SoC based system. Other bus or IX systems may beincluded, such as an I2C interface, an SPI interface, point to pointinterfaces, and a power bus, among others.

FIG. 5 illustrates an example of a platform 500 (or “device 500”). Insome examples, the computer platform 500 may be suitable for use as UEs101, 201, 301, application servers 130, or any other component or devicediscussed herein. The platform 500 may include any combinations of thecomponents shown in the example. The components of platform 500 (orportions thereof) may be implemented as integrated circuits (ICs),discrete electronic devices, or other modules, logic, hardware,software, firmware, or a combination of them adapted in the computerplatform 500, or as components otherwise incorporated within a chassisof a larger system. The block diagram of FIG. 5 is intended to show ahigh level view of components of the platform 500. However, in someexamples, the platform 500 may include fewer, additional, or alternativecomponents, or a different arrangement of the components shown in FIG. 5.

The application circuitry 505 includes circuitry such as, but notlimited to, one or more processors (or processor cores), cache memory,and one or more of LDOs, interrupt controllers, serial interfaces suchas SPI, I2C or universal programmable serial interface module, RTC,timer-counters including interval and watchdog timers, general purposeI/O, memory card controllers such as SD MMC or similar, USB interfaces,MIPI interfaces, and JTAG test access ports. The processors (or cores)of the application circuitry 505 may be coupled with or may includememory/storage elements and may be configured to execute instructionsstored in the memory or storage to enable various applications oroperating systems to run on the system 500. In some examples, the memoryor storage elements may be on-chip memory circuitry, which may includeany suitable volatile or non-volatile memory, such as DRAM, SRAM, EPROM,EEPROM, Flash memory, solid-state memory, or combinations of them, amongother types of memory.

The processor(s) of application circuitry 405 may include, for example,one or more processor cores, one or more application processors, one ormore GPUs, one or more RISC processors, one or more ARM processors, oneor more CISC processors, one or more DSP, one or more FPGAs, one or morePLDs, one or more ASICs, one or more microprocessors or controllers, amultithreaded processor, an ultra-low voltage processor, an embeddedprocessor, some other known processing element, or any suitablecombination thereof. In some examples, the application circuitry 405 mayinclude, or may be, a special-purpose processor/controller to carry outthe techniques described herein.

As examples, the processor(s) of application circuitry 505 may includean Apple A-series processor. The processors of the application circuitry1105 may also be one or more of an Intel® Architecture Core™ basedprocessor, such as a Quark™, an Atom™, an i3, an i5, an i7, or anMCU-class processor, or another such processor available from Intel®Corporation, Santa Clara, CA; Advanced Micro Devices (AMD) Ryzen®processor(s) or Accelerated Processing Units (APUs); Snapdragon™processor(s) from Qualcomm® Technologies, Inc., Texas Instruments, Inc.®Open Multimedia Applications Platform (OMAP)™ processor(s); a MIPS-baseddesign from MIPS Technologies, Inc. such as MIPS Warrior M-class,Warrior I-class, and Warrior P-class processors; an ARM-based designlicensed from ARM Holdings, Ltd., such as the ARM Cortex-A, Cortex-R,and Cortex-M family of processors; or the like. In some examples, theapplication circuitry 505 may be a part of a system on a chip (SoC) inwhich the application circuitry 505 and other components are formed intoa single integrated circuit, or a single package.

Additionally or alternatively, the application circuitry 505 may includecircuitry such as, but not limited to, one or more a field-programmabledevices (FPDs) such as FPGAs; programmable logic devices (PLDs) such ascomplex PLDs (CPLDs), high-capacity PLDs (HCPLDs); ASICs such asstructured ASICs; programmable SoCs (PSoCs), or combinations of them,among others. In some examples, the application circuitry 505 mayinclude logic blocks or logic fabric, and other interconnected resourcesthat may be programmed to perform various functions, such as theprocedures, methods, functions described herein. In some examples, theapplication circuitry 505 may include memory cells (e.g., erasableprogrammable read-only memory (EPROM), electrically erasableprogrammable read-only memory (EEPROM), flash memory, static memory(e.g., static random access memory (SRAM), or anti-fuses)) used to storelogic blocks, logic fabric, data, or other data in look-up tables (LUTs)and the like.

The baseband circuitry 510 may be implemented, for example, as asolder-down substrate including one or more integrated circuits, asingle packaged integrated circuit soldered to a main circuit board or amulti-chip module containing two or more integrated circuits. Thevarious hardware electronic elements of baseband circuitry 510 arediscussed with regard to FIG. 6 .

The RFEMs 515 may comprise a millimeter wave (mmWave) RFEM and one ormore sub-mmWave radio frequency integrated circuits (RFICs). In someexamples, the one or more sub-mmWave RFICs may be physically separatedfrom the mmWave RFEM. The RFICs may include connections to one or moreantennas or antenna arrays (see, e.g., antenna array 611 of FIG. 6 ),and the RFEM may be connected to multiple antennas. In some examples,both mmWave and sub-mmWave radio functions may be implemented in thesame physical RFEM 515, which incorporates both mmWave antennas andsub-mmWave.

The memory circuitry 520 may include any number and type of memorydevices used to provide for a given amount of system memory. Asexamples, the memory circuitry 520 may include one or more of volatilememory, such as random access memory (RAM), dynamic RAM (DRAM) orsynchronous dynamic RAM (SDRAM), and nonvolatile memory (NVM), such ashigh-speed electrically erasable memory (commonly referred to as Flashmemory), phase change random access memory (PRAM), or magnetoresistiverandom access memory (MRAM), or combinations of them, among others. Thememory circuitry 520 may be developed in accordance with a JointElectron Devices Engineering Council (JEDEC) low power double data rate(LPDDR)-based design, such as LPDDR2, LPDDR3, LPDDR4, or the like.Memory circuitry 520 may be implemented as one or more of solder downpackaged integrated circuits, single die package (SDP), dual die package(DDP) or quad die package (Q17P), socketed memory modules, dual inlinememory modules (DIMMs) including microDIMMs or MiniDIMMs, or solderedonto a motherboard using a ball grid array (BGA). In low powerimplementations, the memory circuitry 520 may be on-die memory orregisters associated with the application circuitry 505. To provide forpersistent storage of information such as data, applications, operatingsystems and so forth, memory circuitry 520 may include one or more massstorage devices, which may include, for example, a solid state diskdrive (SSDD), hard disk drive (HDD), a micro HDD, resistance changememories, phase change memories, holographic memories, or chemicalmemories, among others. In some examples, the computer platform 500 mayincorporate the three-dimensional (3D) cross-point (XPOINT) memoriesfrom Intel® and Micron®.

The removable memory circuitry 523 may include devices, circuitry,enclosures, housings, ports or receptacles, among others, used to coupleportable data storage devices with the platform 500. These portable datastorage devices may be used for mass storage purposes, and may include,for example, flash memory cards (e.g., Secure Digital (SD) cards,microSD cards, xD picture cards), and USB flash drives, optical discs,or external HDDs, or combinations of them, among others.

The platform 500 may also include interface circuitry (not shown) forconnecting external devices with the platform 500. The external devicesconnected to the platform 500 using the interface circuitry includesensor circuitry 521 and electromechanical components (EMCs) 522, aswell as removable memory devices coupled to removable memory circuitry523.

The sensor circuitry 521 include devices, modules, or subsystems whosepurpose is to detect events or changes in its environment and send theinformation (e.g., sensor data) about the detected events to one or moreother devices, modules, or subsystems. Examples of such sensors includeinertial measurement units (IMUs) such as accelerometers, gyroscopes, ormagnetometers; microelectromechanical systems (MEMS) ornanoelectromechanical systems (NEMS) including 3-axis accelerometers,3-axis gyroscopes, or magnetometers; level sensors; flow sensors;temperature sensors (e.g., thermistors); pressure sensors; barometricpressure sensors: gravimeters; altimeters; image capture devices (e.g.,cameras or lensless apertures); light detection and ranging (LiDAR)sensors; proximity sensors (e.g., infrared radiation detector and thelike), depth sensors, ambient light sensors, ultrasonic transceivers;microphones or other audio capture devices, or combinations of them,among others.

The EMCs 522 include devices, modules, or subsystems whose purpose is toenable the platform 500 to change its state, position, or orientation,or move or control a mechanism, system, or subsystem. Additionally, theEMCs 522 may be configured to generate and send messages or signaling toother components of the platform 500 to indicate a current state of theEMCs 522. Examples of the EMCs 522 include one or more power switches,relays, such as electromechanical relays (EMRs) or solid state relays(SSRs), actuators (e.g., valve actuators), an audible sound generator, avisual warning device, motors (e.g., DC motors or stepper motors),wheels, thrusters, propellers, claws, clamps, hooks, or combinations ofthem, among other electromechanical components. In some examples, theplatform 500 is configured to operate one or more EMCs 522 based on oneor more captured events, instructions, or control signals received froma service provider or clients, or both.

In some examples, the interface circuitry may connect the platform 500with positioning circuitry 545. The positioning circuitry 545 includescircuitry to receive and decode signals transmitted or broadcasted by apositioning network of a GNSS. Examples of a GNSS include United States'GPS, Russia's GLONASS, the European Union's Galileo system, China'sBeiDou Navigation Satellite System, a regional navigation system or GNSSaugmentation system (e.g., NAVIC), Japan's QZSS, France's DORIS, amongother systems. The positioning circuitry 545 comprises various hardwareelements (e.g., including hardware devices such as switches, filters,amplifiers, antenna elements, and the like to facilitate OTAcommunications) to communicate with components of a positioning network,such as navigation satellite constellation nodes. In some examples, thepositioning circuitry 545 may include a Micro-PNT IC that uses a mastertiming clock to perform position tracking or estimation without GNSSassistance. The positioning circuitry 545 may also be part of, orinteract with, the baseband circuitry 410 or RFEMs 515, or both, tocommunicate with the nodes and components of the positioning network.The positioning circuitry 545 may also provide data (e.g., positiondata, time data) to the application circuitry 505, which may use thedata to synchronize operations with various infrastructure (e.g., radiobase stations), for turn-by-turn navigation applications, or the like.

In some examples, the interface circuitry may connect the platform 500with Near-Field Communication (NFC) circuitry 540. The NFC circuitry 540is configured to provide contactless, short-range communications basedon radio frequency identification (RFID) standards, in which magneticfield induction is used to enable communication between NFC circuitry540 and NFC-enabled devices external to the platform 500 (e.g., an “NFCtouchpoint”). The NFC circuitry 540 includes an NFC controller coupledwith an antenna element and a processor coupled with the NFC controller.The NFC controller may be a chip or IC providing NFC functionalities tothe NFC circuitry 540 by executing NFC controller firmware and an NFCstack. The NFC stack may be executed by the processor to control the NFCcontroller, and the NFC controller firmware may be executed by the NFCcontroller to control the antenna element to emit short-range RFsignals. The RF signals may power a passive NFC tag (e.g., a microchipembedded in a sticker or wristband) to transmit stored data to the NFCcircuitry 540, or initiate data transfer between the NFC circuitry 540and another active NFC device (e.g., a smartphone or an NFC-enabled POSterminal) that is proximate to the platform 500.

The driver circuitry 546 may include software and hardware elements thatoperate to control particular devices that are embedded in the platform500, attached to the platform 500, or otherwise communicatively coupledwith the platform 500. The driver circuitry 546 may include individualdrivers allowing other components of the platform 500 to interact withor control various input/output (I/O) devices that may be presentwithin, or connected to, the platform 500. For example, the drivercircuitry 546 may include a display driver to control and allow accessto a display device, a touchscreen driver to control and allow access toa touchscreen interface of the platform 500, sensor drivers to obtainsensor readings of sensor circuitry 521 and control and allow access tosensor circuitry 521, EMC drivers to obtain actuator positions of theEMCs 522 or control and allow access to the EMCs 522, a camera driver tocontrol and allow access to an embedded image capture device, audiodrivers to control and allow access to one or more audio devices.

The power management integrated circuitry (PMIC) 525 (also referred toas “power management circuitry 525”) may manage power provided tovarious components of the platform 500. In particular, with respect tothe baseband circuitry 510, the PMIC 525 may control power-sourceselection, voltage scaling, battery charging, or DC-to-DC conversion.The PMIC 525 may be included when the platform 500 is capable of beingpowered by a battery 530, for example, when the device is included in aUE 101, 201, 301.

In some examples, the PMIC 525 may control, or otherwise be part of,various power saving mechanisms of the platform 500. For example, if theplatform 500 is in an RRC_Connected state, where it is still connectedto the RAN node as it expects to receive traffic shortly, then it mayenter a state known as Discontinuous Reception Mode (DRX) after a periodof inactivity. During this state, the platform 500 may power down forbrief intervals of time and thus save power. If there is no data trafficactivity for an extended period of time, then the platform 500 maytransition off to an RRC_Idle state, where it disconnects from thenetwork and does not perform operations such as channel quality feedbackor handover. This can allow the platform 500 to enter a very low powerstate, where it periodically wakes up to listen to the network and thenpowers down again. In some examples, the platform 500 may not receivedata in the RRC_Idle state and instead must transition back toRRC_Connected state to receive data. An additional power saving mode mayallow a device to be unavailable to the network for periods longer thana paging interval (ranging from seconds to a few hours). During thistime, the device may be unreachable to the network and may power downcompletely. Any data sent during this time may incurs a large delay andit is assumed the delay is acceptable.

A battery 530 may power the platform 500, although in some examples theplatform 500 may be deployed in a fixed location, and may have a powersupply coupled to an electrical grid. The battery 530 may be a lithiumion battery, a metal-air battery, such as a zinc-air battery, analuminum-air battery, or a lithium-air battery, among others. In someexamples, such as in V2X applications, the battery 530 may be a typicallead-acid automotive battery.

In some examples, the battery 530 may be a “smart battery,” whichincludes or is coupled with a Battery Management System (BMS) or batterymonitoring integrated circuitry. The BMS may be included in the platform500 to track the state of charge (SoCh) of the battery 530. The BMS maybe used to monitor other parameters of the battery 530 to providefailure predictions, such as the state of health (SoH) and the state offunction (SoF) of the battery 530. The BMS may communicate theinformation of the battery 530 to the application circuitry 505 or othercomponents of the platform 500. The BMS may also include ananalog-to-digital (ADC) convertor that allows the application circuitry505 to directly monitor the voltage of the battery 530 or the currentflow from the battery 530. The battery parameters may be used todetermine actions that the platform 500 may perform, such astransmission frequency, network operation, or sensing frequency, amongothers.

A power block, or other power supply coupled to an electrical grid maybe coupled with the BMS to charge the battery 530. In some examples, thepower block 530 may be replaced with a wireless power receiver to obtainthe power wirelessly, for example, through a loop antenna in thecomputer platform 500. In these examples, a wireless battery chargingcircuit may be included in the BMS. The specific charging circuitschosen may depend on the size of the battery 530, and thus, the currentrequired. The charging may be performed using the Airfuel standardpromulgated by the Airfuel Alliance, the Qi wireless charging standardpromulgated by the Wireless Power Consortium, or the Rezence chargingstandard promulgated by the Alliance for Wireless Power, among others.

The user interface circuitry 550 includes various input/output (110)devices present within, or connected to, the platform 500, and includesone or more user interfaces designed to enable user interaction with theplatform 500 or peripheral component interfaces designed to enableperipheral component interaction with the platform 500. The userinterface circuitry 550 includes input device circuitry and outputdevice circuitry. Input device circuitry includes any physical orvirtual means for accepting an input including one or more physical orvirtual buttons (e.g., a reset button), a physical keyboard, keypad,mouse, touchpad, touchscreen, microphones, scanner, or headset, orcombinations of them, among others. The output device circuitry includesany physical or virtual means for showing information or otherwiseconveying information, such as sensor readings, actuator position(s), orother information. Output device circuitry may include any number orcombinations of audio or visual display, including one or more simplevisual outputs or indicators (e.g., binary status indicators (e.g.,light emitting diodes (LEDs)), multi-character visual outputs, or morecomplex outputs such as display devices or touchscreens (e.g., LiquidChrystal Displays (LCD), LED displays, quantum dot displays, orprojectors), with the output of characters, graphics, or multimediaobjects being generated or produced from the operation of the platform500. The output device circuitry may also include speakers or otheraudio emitting devices, or printer(s). In some examples, the sensorcircuitry 521 may be used as the input device circuitry (e.g., an imagecapture device or motion capture device), and one or more EMCs may beused as the output device circuitry (e.g., an actuator to provide hapticfeedback). In another example, NFC circuitry comprising an NFCcontroller coupled with an antenna element and a processing device maybe included to read electronic tags or connect with another NFC-enableddevice. Peripheral component interfaces may include, but are not limitedto, a non-volatile memory port, a USB port, an audio jack, or a powersupply interface.

Although not shown, the components of platform 500 may communicate withone another using a suitable bus or interconnect (IX) technology, whichmay include any number of technologies, including ISA, EISA, PCI, PCIx,PCIe, a Time-Trigger Protocol (TTP) system, a FlexRay system, or anynumber of other technologies. The bus or IX may be a proprietary bus orIX, for example, used in a SoC based system. Other bus or IX systems maybe included, such as an I2C interface, an SPI interface, point-to-pointinterfaces, and a power bus, among others.

FIG. 6 illustrates example components of baseband circuitry 610 andradio front end modules (RFEM) 615. The baseband circuitry 610 cancorrespond to the baseband circuitry 410 and 510 of FIGS. 4 and 5 ,respectively. The RFEM 615 can correspond to the RFEM 415 and 515 ofFIGS. 4 and 5 , respectively. As shown, the RFEMs 615 may include RadioFrequency (RF) circuitry 606, front-end module (FEM) circuitry 608,antenna array 611 coupled together.

The baseband circuitry 610 includes circuitry or control logic, or both,configured to carry out various radio or network protocol and controlfunctions that enable communication with one or more radio networksusing the RF circuitry 606. The radio control functions may include, butare not limited to, signal modulation and demodulation, encoding anddecoding, and radio frequency shifting. In some examples, modulation anddemodulation circuitry of the baseband circuitry 610 may includeFast-Fourier Transform (FFT), precoding, or constellation mapping anddemapping functionality. In some examples, encoding and decodingcircuitry of the baseband circuitry 610 may include convolution,tail-biting convolution, turbo, Viterbi, or Low Density Parity Check(LDPC) encoder and decoder functionality. Modulation and demodulationand encoder and decoder functionality are not limited to these examplesand may include other suitable functionality in other examples. Thebaseband circuitry 610 is configured to process baseband signalsreceived from a receive signal path of the RF circuitry 606 and togenerate baseband signals for a transmit signal path of the RF circuitry606. The baseband circuitry 610 is configured to interface withapplication circuitry (e.g., the application circuitry 405, 505 shown inFIGS. 4 and 5 ) for generation and processing of the baseband signalsand for controlling operations of the RF circuitry 606. The basebandcircuitry 610 may handle various radio control functions.

The aforementioned circuitry and control logic of the baseband circuitry610 may include one or more single or multi-core processors. Forexample, the one or more processors may include a 3G baseband processor604A, a 4G or LTE baseband processor 604B, a 5G or NR baseband processor604C, or some other baseband processor(s) 604D for other existinggenerations, generations in development or to be developed in the future(e.g., sixth generation (6G)). In some examples, some or all of thefunctionality of baseband processors 604A-D may be included in modulesstored in the memory 604G and executed using a Central Processing Unit(CPU) 604E. In some examples, some or all of the functionality ofbaseband processors 604A-D may be provided as hardware accelerators(e.g., FPGAs or ASICs) loaded with the appropriate bit streams or logicblocks stored in respective memory cells. In some examples, the memory604G may store program code of a real-time OS (RTOS) which, whenexecuted by the CPU 604E (or other baseband processor), is to cause theCPU 604E (or other baseband processor) to manage resources of thebaseband circuitry 610, schedule tasks, or carry out other operations.Examples of the RTOS may include Operating System Embedded (OSE)™provided by Enea®, Nucleus RTOS™ provided by Mentor Graphics®, VersatileReal-Time Executive (VRTX) provided by Mentor Graphics®, ThreadX™provided by Express Logic®, FreeRTOS, REX OS provided by Qualcomm®, OKL4provided by Open Kernel (OK) Labs®, or any other suitable RTOS, such asthose discussed herein. In addition, the baseband circuitry 610 includesone or more audio digital signal processor(s) (DSP) 604F. The audioDSP(s) 604F include elements for compression and decompression and echocancellation and may include other suitable processing elements in someexamples.

In some examples, each of the processors 604A-604E include respectivememory interfaces to send and receive data to and from the memory 604G.The baseband circuitry 610 may further include one or more interfaces tocommunicatively couple to other circuitries or devices, such as aninterface to send and receive data to and from memory external to thebaseband circuitry 610; an application circuitry interface to send andreceive data to and from the application circuitry 405, 505 of FIGS. 4and 6 ); an RF circuitry interface to send and receive data to and fromRF circuitry 606 of FIG. 6 ; a wireless hardware connectivity interfaceto send and receive data to and from one or more wireless hardwareelements (e.g., Near Field Communication (NFC) components,Bluetooth®/Bluetooth® Low Energy components, Wi-Fi® components, and/orthe like); and a power management interface to send and receive power orcontrol signals to and from the PMIC 525.

In some examples (which may be combined with the above describedexamples), the baseband circuitry 610 includes one or more digitalbaseband systems, which are coupled with one another using aninterconnect subsystem and to a CPU subsystem, an audio subsystem, andan interface subsystem. The digital baseband subsystems may also becoupled to a digital baseband interface and a mixed-signal basebandsubsystem using another interconnect subsystem. Each of the interconnectsubsystems may include a bus system, point-to-point connections,network-on-chip (NOC) structures, or some other suitable bus orinterconnect technology, such as those discussed herein. The audiosubsystem may include DSP circuitry, buffer memory, program memory,speech processing accelerator circuitry, data converter circuitry suchas analog-to-digital and digital-to-analog converter circuitry, analogcircuitry including one or more of amplifiers and filters, among othercomponents. In some examples, the baseband circuitry 610 may includeprotocol processing circuitry with one or more instances of controlcircuitry (not shown) to provide control functions for the digitalbaseband circuitry or radio frequency circuitry (e.g., the radio frontend modules 615).

Although not shown in FIG. 6 , in some examples, the baseband circuitry610 includes individual processing device(s) to operate one or morewireless communication protocols (e.g., a “multi-protocol basebandprocessor” or “protocol processing circuitry”) and individual processingdevice(s) to implement PHY layer functions. In some examples, the PHYlayer functions include the aforementioned radio control functions. Insome examples, the protocol processing circuitry operates or implementsvarious protocol layers or entities of one or more wirelesscommunication protocols. For example, the protocol processing circuitrymay operate LTE protocol entities or 5G NR protocol entities, or both,when the baseband circuitry 610 or RF circuitry 606, or both, are partof mmWave communication circuitry or some other suitable cellularcommunication circuitry. In this example, the protocol processingcircuitry can operate MAC, RLC, PDCP, SDAP, RRC, and NAS functions. Insome examples, the protocol processing circuitry may operate one or moreIEEE-based protocols when the baseband circuitry 610 or RF circuitry606, or both, are part of a Wi-Fi communication system. In this example,the protocol processing circuitry can operate Wi-Fi MAC and logical linkcontrol (LLC) functions. The protocol processing circuitry may includeone or more memory structures (e.g., 604G) to store program code anddata for operating the protocol functions, as well as one or moreprocessing cores to execute the program code and perform variousoperations using the data. The baseband circuitry 610 may also supportradio communications for more than one wireless protocol.

The various hardware elements of the baseband circuitry 610 discussedherein may be implemented, for example, as a solder-down substrateincluding one or more integrated circuits (ICs), a single packaged ICsoldered to a main circuit board or a multi-chip module containing twoor more ICs. In some examples, the components of the baseband circuitry610 may be suitably combined in a single chip or chipset, or disposed ona same circuit board. In some examples, some or all of the constituentcomponents of the baseband circuitry 610 and RF circuitry 606 may beimplemented together such as, for example, a system on a chip (SoC) orSystem-in-Package (SiP). In some examples, some or all of theconstituent components of the baseband circuitry 610 may be implementedas a separate SoC that is communicatively coupled with and RF circuitry606 (or multiple instances of RF circuitry 606). In some examples, someor all of the constituent components of the baseband circuitry 610 andthe application circuitry 405, 505 may be implemented together asindividual SoCs mounted to a same circuit board (e.g., a “multi-chippackage”).

In some examples, the baseband circuitry 610 may provide forcommunication compatible with one or more radio technologies. Forexample, the baseband circuitry 610 may support communication with anE-UTRAN or other WMAN, a WLAN, or a WPAN. Examples in which the basebandcircuitry 610 is configured to support radio communications of more thanone wireless protocol may be referred to as multi-mode basebandcircuitry.

The RF circuitry 606 may enable communication with wireless networksusing modulated electromagnetic radiation through a non-solid medium. Insome examples, the RF circuitry 606 may include switches, filters, oramplifiers, among other components, to facilitate the communication withthe wireless network. The RF circuitry 606 may include a receive signalpath, which may include circuitry to down-convert RF signals receivedfrom the FEM circuitry 608 and provide baseband signals to the basebandcircuitry 610. The RF circuitry 606 may also include a transmit signalpath, which may include circuitry to up-convert baseband signalsprovided by the baseband circuitry 610 and provide RF output signals tothe FEM circuitry 608 for transmission.

The receive signal path of the RF circuitry 606 includes mixer circuitry606 a, amplifier circuitry 606 b and filter circuitry 606 c. In someexamples, the transmit signal path of the RF circuitry 606 may includefilter circuitry 606 c and mixer circuitry 606 a. The RF circuitry 606also includes synthesizer circuitry 606 d for synthesizing a frequencyfor use by the mixer circuitry 606 a of the receive signal path and thetransmit signal path. In some examples, the mixer circuitry 606 a of thereceive signal path may be configured to down-convert RF signalsreceived from the FEM circuitry 608 based on the synthesized frequencyprovided by synthesizer circuitry 606 d. The amplifier circuitry 606 bmay be configured to amplify the down-converted signals and the filtercircuitry 606 c may be a low-pass filter (LPF) or band-pass filter (BPF)configured to remove unwanted signals from the down-converted signals togenerate output baseband signals. Output baseband signals may beprovided to the baseband circuitry 610 for further processing. In someexamples, the output baseband signals may be zero-frequency basebandsignals, although this is not a requirement. In some examples, the mixercircuitry 606 a of the receive signal path may comprise passive mixers.

In some examples, the mixer circuitry 606 a of the transmit signal pathmay be configured to up-convert input baseband signals based on thesynthesized frequency provided by the synthesizer circuitry 606 d togenerate RF output signals for the FEM circuitry 608. The basebandsignals may be provided by the baseband circuitry 610 and may befiltered by filter circuitry 606 c.

In some examples, the mixer circuitry 606 a of the receive signal pathand the mixer circuitry 606 a of the transmit signal path may includetwo or more mixers and may be arranged for quadrature downconversion andupconversion, respectively. In some examples, the mixer circuitry 606 aof the receive signal path and the mixer circuitry 606 a of the transmitsignal path may include two or more mixers and may be arranged for imagerejection (e.g., Hartley image rejection). In some examples, the mixercircuitry 606 a of the receive signal path and the mixer circuitry 606 aof the transmit signal path may be arranged for direct downconversionand direct upconversion, respectively. In some examples, the mixercircuitry 606 a of the receive signal path and the mixer circuitry 606 aof the transmit signal path may be configured for super-heterodyneoperation.

In some examples, the output baseband signals and the input basebandsignals may be analog baseband signals. In some examples, the outputbaseband signals and the input baseband signals may be digital basebandsignals, and the RF circuitry 606 may include analog-to-digitalconverter (ADC) and digital-to-analog converter (DAC) circuitry and thebaseband circuitry 610 may include a digital baseband interface tocommunicate with the RF circuitry 606.

In some dual-mode examples, a separate radio IC circuitry may beprovided for processing signals for each spectrum, although thetechniques described here are not limited in this respect.

In some examples, the synthesizer circuitry 606 d may be a fractional-Nsynthesizer or a fractional N/N+1 synthesizer, although other types offrequency synthesizers may used. For example, synthesizer circuitry 606d may be a delta-sigma synthesizer, a frequency multiplier, or asynthesizer comprising a phase-locked loop with a frequency divider.

The synthesizer circuitry 606 d may be configured to synthesize anoutput frequency for use by the mixer circuitry 606 a of the RFcircuitry 606 based on a frequency input and a divider control input. Insome examples, the synthesizer circuitry 606 d may be a fractional N/N+1synthesizer.

In some examples, frequency input may be provided by a voltagecontrolled oscillator (VCO), although that is not a requirement. Dividercontrol input may be provided by either the baseband circuitry 610 orthe application circuitry 405/505 depending on the desired outputfrequency. In some examples, a divider control input (e.g., N) may bedetermined from a look-up table based on a channel indicated by theapplication circuitry 405, 505.

The synthesizer circuitry 606 d of the RF circuitry 606 may include adivider, a delay-locked loop (DLL), a multiplexer and a phaseaccumulator. In some examples, the divider may be a dual modulus divider(DMD) and the phase accumulator may be a digital phase accumulator(DPA). In some examples, the DMD may be configured to divide the inputsignal by either N or N+1 (e.g., based on a carry out) to provide afractional division ratio. In some examples, the DLL may include a setof cascaded, tunable, delay elements, a phase detector, a charge pumpand a D-type flip-flop. The delay elements may be configured to break aVCO period up into Nd equal packets of phase, where Nd is the number ofdelay elements in the delay line. In this way, the DLL provides negativefeedback to help ensure that the total delay through the delay line isone VCO cycle.

In some examples, synthesizer circuitry 606 d may be configured togenerate a carrier frequency as the output frequency, while in otherexamples, the output frequency may be a multiple of the carrierfrequency (e.g., twice the carrier frequency, four times the carrierfrequency) and used in conjunction with quadrature generator and dividercircuitry to generate multiple signals at the carrier frequency withmultiple different phases with respect to each other. In some examples,the output frequency may be a LO frequency (fLO). In some examples, theRF circuitry 606 may include an IQ or polar converter.

The FEM circuitry 608 may include a receive signal path, which mayinclude circuitry configured to operate on RF signals received fromantenna array 611, amplify the received signals and provide theamplified versions of the received signals to the RF circuitry 606 forfurther processing. The FEM circuitry 608 may also include a transmitsignal path, which may include circuitry configured to amplify signalsfor transmission provided by the RF circuitry 606 for transmission byone or more of antenna elements of antenna array 611. The amplificationthrough the transmit or receive signal paths may be done solely in theRF circuitry 606, solely in the FEM circuitry 608, or in both the RFcircuitry 606 and the FEM circuitry 608.

In some examples, the FEM circuitry 608 may include a TX/RX switch toswitch between transmit mode and receive mode operation. The FEMcircuitry 608 may include a receive signal path and a transmit signalpath. The receive signal path of the FEM circuitry 608 may include anLNA to amplify received RF signals and provide the amplified received RFsignals as an output (e.g., to the RF circuitry 606). The transmitsignal path of the FEM circuitry 608 may include a power amplifier (PA)to amplify input RF signals (e.g., provided by RF circuitry 606), andone or more filters to generate RF signals for subsequent transmissionby one or more antenna elements of the antenna array 611.

The antenna array 611 comprises one or more antenna elements, each ofwhich is configured convert electrical signals into radio waves totravel through the air and to convert received radio waves intoelectrical signals. For example, digital baseband signals provided bythe baseband circuitry 610 is converted into analog RF signals (e.g.,modulated waveform) that will be amplified and transmitted using theantenna elements of the antenna array 611 including one or more antennaelements (not shown). The antenna elements may be omnidirectional,directional, or a combination thereof. The antenna elements may beformed in a multitude of arranges as are known and/or discussed herein.The antenna array 611 may comprise microstrip antennas or printedantennas that are fabricated on the surface of one or more printedcircuit boards. The antenna array 611 may be formed as a patch of metalfoil (e.g., a patch antenna) in a variety of shapes, and may be coupledwith the RF circuitry 606 and/or FEM circuitry 608 using metaltransmission lines or the like.

Processors of the application circuitry 405/505 and processors of thebaseband circuitry 610 may be used to execute elements of one or moreinstances of a protocol stack. For example, processors of the basebandcircuitry 610, alone or in combination, may be used execute Layer 3,Layer 2, or Layer 1 functionality, while processors of the applicationcircuitry 405, 505 may utilize data (e.g., packet data) received fromthese layers and further execute Layer 4 functionality (e.g., TCP andUDP layers). As referred to herein, Layer 3 may comprise a RRC layer,described in further detail below. As referred to herein, Layer 2 maycomprise a MAC layer, an RLC layer, and a PDCP layer, described infurther detail below. As referred to herein, Layer 1 may comprise a PHYlayer of a UE/RAN node, described in further detail below.

FIG. 7 illustrates example components of communication circuitry 700. Insome examples, the communication circuitry 700 may be implemented aspart of the system 400 or the platform 500 shown in FIGS. 4 and 5 . Thecommunication circuitry 700 may be communicatively coupled (e.g.,directly or indirectly) to one or more antennas, such as antennas 702a-c. In some examples, the communication circuitry 700 includes or iscommunicatively coupled to dedicated receive chains, processors, orradios, or combinations of them, for multiple RATs (e.g., a firstreceive chain for LTE and a second receive chain for 5G NR). Forexample, as shown in FIG. 7 , the communication circuitry 700 includes amodem 710 and a modem 720, which may correspond to or be a part of thebaseband circuitry 410 and 510 of FIGS. 4 and 5 . The modem 710 may beconfigured for communications according to a first RAT, such as LTE orLTE-A, and the modem 720 may be configured for communications accordingto a second RAT, such as 5G NR.

The modem 710 includes one or more processors 712 and a memory 716 incommunication with the processors 712. The modem 710 is in communicationwith a radio frequency (RF) front end 730, which may correspond to or bea part of to the RFEM 415 and 515 of FIGS. 4 and 5 . The RF front end730 may include circuitry for transmitting and receiving radio signals.For example, the RF front end 730 includes receive circuitry (RX) 732and transmit circuitry (TX) 734. In some examples, the receive circuitry732 is in communication with a DL front end 750, which may includecircuitry for receiving radio signals from the antenna 702 a. A switch770 may selectively couple the modem 710 to an UL front end 772, whichmay include circuitry for transmitting radio signals using the antenna702 c.

Similarly, the modem 720 includes one or more processors 722 and amemory 726 in communication with the processors 722. The modem 720 is incommunication with an RF front end 740, which may correspond to or be apart of to the RFEM 415 and 515 of FIGS. 4 and 5 . The RF front end 740may include circuitry for transmitting and receiving radio signals. Forexample, the RF front end 740 includes receive circuitry 742 andtransmit circuitry 744. In some examples, the receive circuitry 742 isin communication with a DL front end 760, which may include circuitryfor receiving radio signals from the antenna 702 b. The switch 770 mayselectively couple the modem 720 to the UL front end 772 fortransmitting radio signals using the antenna 702 c.

The modem 710 may include hardware and software components for timedivision multiplexing UL data (e.g., for NSA NR operations), as well asthe various other techniques described herein. The processors 712 mayinclude one or more processing elements configured to implement variousfeatures described herein, such as by executing program instructionsstored on the memory 716 (e.g., a non-transitory computer-readablememory medium). In some examples, the processor 712 may be configured asa programmable hardware element, such as a FPGA or an ASIC. In someexamples, the processors 712 may include one or more ICs that areconfigured to perform the functions of processors 712. For example, eachIC may include circuitry configured to perform the functions ofprocessors 712.

The modem 720 may include hardware and software components for timedivision multiplexing UL data (e.g., for NSA NR operations), as well asthe various other techniques described herein. The processors 722 mayinclude one or more processing elements configured to implement variousfeatures described herein, such as by executing instructions stored onthe memory 726 (e.g., a non-transitory computer-readable memory medium).In some examples, the processor 722 may be configured as a programmablehardware element, such as a FPGA or an ASIC. In some examples, theprocessor 722 may include one or more ICs that are configured to performthe functions of processors 722. For example, each IC may includecircuitry configured to perform the functions of processors 522.

FIG. 8 illustrates various protocol functions that may be implemented ina wireless communication device. In particular, FIG. 8 includes anarrangement 800 showing interconnections between various protocollayers/entities. The following description of FIG. 8 is provided forvarious protocol layers and entities that operate in conjunction withthe 5G NR system standards and the LTE system standards, but some or allof the aspects of FIG. 8 may be applicable to other wirelesscommunication network systems as well.

The protocol layers of arrangement 800 may include one or more of PHY810, MAC 820, RLC 830, PDCP 840, SDAP 847, RRC 855, and NAS layer 857,in addition to other higher layer functions not illustrated. Theprotocol layers may include one or more service access points (e.g.,items 859, 856, 850, 849, 845, 835, 825, and 815 in FIG. 8 ) that mayprovide communication between two or more protocol layers.

The PHY 810 may transmit and receive physical layer signals 805 that maybe received from or transmitted to one or more other communicationdevices. The physical layer signals 805 may include one or more physicalchannels, such as those discussed herein. The PHY 810 may furtherperform link adaptation or adaptive modulation and coding (AMC), powercontrol, cell search (e.g., for initial synchronization and handoverpurposes), and other measurements used by higher layers, such as the RRC855. The PHY 810 may still further perform error detection on thetransport channels, forward error correction (FEC) coding and decodingof the transport channels, modulation and demodulation of physicalchannels, interleaving, rate matching, mapping onto physical channels,and MIMO antenna processing. In some examples, an instance of PHY 810may process requests from and provide indications to an instance of MAC820 using one or more PHY-SAP 815. In some examples, requests andindications communicated using PHY-SAP 815 may comprise one or moretransport channels.

Instance(s) of MAC 820 may process requests from, and provideindications to, an instance of RLC 830 using one or more MAC-SAPs 825.These requests and indications communicated using the MAC-SAP 825 mayinclude one or more logical channels. The MAC 820 may perform mappingbetween the logical channels and transport channels, multiplexing of MACSDUs from one or more logical channels onto transport blocks (TBs) to bedelivered to PHY 810 using the transport channels, de-multiplexing MACSDUs to one or more logical channels from TBs delivered from the PHY 810using transport channels, multiplexing MAC SDUs onto TBs, schedulinginformation reporting, error correction through HARQ, and logicalchannel prioritization.

Instance(s) of RLC 830 may process requests from and provide indicationsto an instance of PDCP 840 using one or more radio link control serviceaccess points (RLC-SAP) 835. These requests and indications communicatedusing RLC-SAP 835 may include one or more RLC channels. The RLC 830 mayoperate in a plurality of modes of operation, including: TransparentMode™, Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC 830may execute transfer of upper layer protocol data units (PDUs), errorcorrection through automatic repeat request (ARQ) for AM data transfers,and concatenation, segmentation and reassembly of RLC SDUs for UM and AMdata transfers. The RLC 830 may also execute re-segmentation of RLC dataPDUs for AM data transfers, reorder RLC data PDUs for UM and AM datatransfers, detect duplicate data for UM and AM data transfers, discardRLC SDUs for UM and AM data transfers, detect protocol errors for AMdata transfers, and perform RLC re-establishment.

Instance(s) of PDCP 840 may process requests from and provideindications to instance(s) of RRC 855 or instance(s) of SDAP 847, orboth, using one or more packet data convergence protocol service accesspoints (PDCP-SAP) 845. These requests and indications communicated usingPDCP-SAP 845 may include one or more radio bearers. The PDCP 840 mayexecute header compression and decompression of IP data, maintain PDCPSequence Numbers (SNs), perform in-sequence delivery of upper layer PDUsat re-establishment of lower layers, eliminate duplicates of lower layerSDUs at re-establishment of lower layers for radio bearers mapped on RLCAM, cipher and decipher control plane data, perform integrity protectionand integrity verification of control plane data, control timer-baseddiscard of data, and perform security operations (e.g., ciphering,deciphering, integrity protection, or integrity verification).

Instance(s) of SDAP 847 may process requests from and provideindications to one or more higher layer protocol entities using one ormore SDAP-SAP 849. These requests and indications communicated usingSDAP-SAP 849 may include one or more QoS flows. The SDAP 847 may map QoSflows to data radio bearers (DRBs), and vice versa, and may also markQoS flow identifiers (QFIs) in DL and UL packets. A single SDAP entity847 may be configured for an individual PDU session. In the ULdirection, the NG-RAN 110 may control the mapping of QoS Flows to DRB(s)in two different ways, reflective mapping or explicit mapping. Forreflective mapping, the SDAP 847 of a UE 101 may monitor the QFIs of theDL packets for each DRB, and may apply the same mapping for packetsflowing in the UL direction. For a DRB, the SDAP 847 of the UE 101 maymap the UL packets belonging to the QoS flows(s) corresponding to theQoS flow ID(s) and PDU session observed in the DL packets for that DRB.To enable reflective mapping, the NG-RAN 310 may mark DL packets overthe Uu interface with a QoS flow ID. The explicit mapping may involvethe RRC 855 configuring the SDAP 847 with an explicit QoS flow to DRBmapping rule, which may be stored and followed by the SDAP 847. In someexamples, the SDAP 847 may only be used in NR implementations and maynot be used in LTE implementations.

The RRC 855 may configure, using one or more management service accesspoints (M-SAP), aspects of one or more protocol layers, which mayinclude one or more instances of PHY 810, MAC 820, RLC 830, PDCP 840 andSDAP 847. In some examples, an instance of RRC 855 may process requestsfrom and provide indications to one or more NAS entities 857 using oneor more RRC-SAPs 856. The main services and functions of the RRC 855 mayinclude broadcast of system information (e.g., included in masterinformation blocks (MIBs) or system information blocks (SIBs) related tothe NAS), broadcast of system information related to the access stratum(AS), paging, establishment, maintenance and release of an RRCconnection between the UE 101 and RAN 110 (e.g., RRC connection paging,RRC connection establishment, RRC connection modification, and RRCconnection release), establishment, configuration, maintenance andrelease of point to point Radio Bearers, security functions includingkey management, inter-RAT mobility, and measurement configuration for UEmeasurement reporting. The MIBs and SIBs may comprise one or moreinformation elements, which may each comprise individual data fields ordata structures.

The NAS 857 may form the highest stratum of the control plane betweenthe UE 101 and the AMF 321. The NAS 857 may support the mobility of theUEs 101 and the session management procedures to establish and maintainIP connectivity between the UE 101 and a P-GW in LTE systems.

In some examples, one or more protocol entities of arrangement 800 maybe implemented in UEs 101, RAN nodes 111, AMF 321 in NR implementationsor MME 221 in LTE implementations, UPF 302 in NR implementations or S-GW222 and P-GW 223 in LTE implementations, or the like to be used forcontrol plane or user plane communications protocol stack between theaforementioned devices. In some examples, one or more protocol entitiesthat may be implemented in one or more of UE 101, gNB 111, AMF 321,among others, may communicate with a respective peer protocol entitythat may be implemented in or on another device using the services ofrespective lower layer protocol entities to perform such communication.In some examples, a gNB-CU of the gNB 111 may host the RRC 855, SDAP847, and PDCP 840 of the gNB that controls the operation of one or moregNB-DUs, and the gNB-DUs of the gNB 111 may each host the RLC 830, MAC820, and PHY 810 of the gNB 111.

In some examples, a control plane protocol stack may include, in orderfrom highest layer to lowest layer, NAS 857, RRC 855, PDCP 840, RLC 830,MAC 820, and PHY 810. In this example, upper layers 860 may be built ontop of the NAS 857, which includes an IP layer 861, an SCTP 862, and anapplication layer signaling protocol (AP) 863.

In some examples, such as NR implementations, the AP 863 may be an NGapplication protocol layer (NGAP or NG-AP) 863 for the NG interface 113defined between the NG-RAN node 111 and the AMF 321, or the AP 863 maybe an Xn application protocol layer (XnAP or Xn-AP) 863 for the Xninterface 112 that is defined between two or more RAN nodes 111.

The NG-AP 863 may support the functions of the NG interface 113 and maycomprise elementary procedures (EPs). An NG-AP EP may be a unit ofinteraction between the NG-RAN node 111 and the AMF 321. The NG-AP 863services may include two groups: UE-associated services (e.g., servicesrelated to a UE 101) and non-UE-associated services (e.g., servicesrelated to the whole NG interface instance between the NG-RAN node 111and AMF 321). These services may include functions such as, but notlimited to: a paging function for the sending of paging requests toNG-RAN nodes 111 involved in a particular paging area; a UE contextmanagement function for allowing the AMF 321 to establish, modify, orrelease a UE context in the AMF 321 and the NG-RAN node 111; a mobilityfunction for UEs 101 in ECM-CONNECTED mode for intra-system HOs tosupport mobility within NG-RAN and inter-system HOs to support mobilityfrom/to EPS systems; a NAS Signaling Transport function for transportingor rerouting NAS messages between UE 101 and AMF 321; a NAS nodeselection function for determining an association between the AMF 321and the UE 101; NG interface management function(s) for setting up theNG interface and monitoring for errors over the NG interface; a warningmessage transmission function for providing means to transfer warningmessages using NG interface or cancel ongoing broadcast of warningmessages; a configuration transfer function for requesting andtransferring of RAN configuration information (e.g., SON information orperformance measurement (PM) data) between two RAN nodes 111 using CN120, or combinations of them, among others.

The XnAP 863 may support the functions of the Xn interface 112 and maycomprise XnAP basic mobility procedures and XnAP global procedures. TheXnAP basic mobility procedures may comprise procedures used to handle UEmobility within the NG RAN 111 (or E-UTRAN 210), such as handoverpreparation and cancellation procedures, SN Status Transfer procedures,UE context retrieval and UE context release procedures, RAN pagingprocedures, or dual connectivity related procedures, among others. TheXnAP global procedures may comprise procedures that are not related to aspecific UE 101, such as Xn interface setup and reset procedures, NG-RANupdate procedures, or cell activation procedures, among others.

In LTE implementations, the AP 863 may be an S1 Application Protocollayer (S1-AP) 863 for the S1 interface 113 defined between an E-UTRANnode 111 and an MME, or the AP 863 may be an X2 application protocollayer (X2AP or X2-AP) 863 for the X2 interface 112 that is definedbetween two or more E-UTRAN nodes 111.

The S1 Application Protocol layer (S1-AP) 863 may support the functionsof the S1 interface, and similar to the NG-AP discussed previously, theS1-AP may include S1-AP EPs. An S1-AP EP may be a unit of interactionbetween the E-UTRAN node 111 and an MME 221 within an LTE CN 120. TheS1-AP 863 services may comprise two groups: UE-associated services andnon UE-associated services. These services perform functions including,but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UEcapability indication, mobility, NAS signaling transport, RANInformation Management (RIM), and configuration transfer.

The X2AP 863 may support the functions of the X2 interface 112 and mayinclude X2AP basic mobility procedures and X2AP global procedures. TheX2AP basic mobility procedures may include procedures used to handle UEmobility within the E-UTRAN 120, such as handover preparation andcancellation procedures, SN Status Transfer procedures, UE contextretrieval and UE context release procedures, RAN paging procedures, ordual connectivity related procedures, among others. The X2AP globalprocedures may comprise procedures that are not related to a specific UE101, such as X2 interface setup and reset procedures, load indicationprocedures, error indication procedures, or cell activation procedures,among others.

The SCTP layer (alternatively referred to as the SCTP/IP layer) 862 mayprovide guaranteed delivery of application layer messages (e.g., NGAP orXnAP messages in NR implementations, or S1-AP or X2AP messages in LTEimplementations). The SCTP 862 may ensure reliable delivery of signalingmessages between the RAN node 111 and the AMF 321/MME 221 based in parton the IP protocol, supported by the IP 861. The Internet Protocol layer(IP) 861 may be used to perform packet addressing and routingfunctionality. In some implementations the IP layer 861 may usepoint-to-point transmission to deliver and convey PDUs. In this regard,the RAN node 111 may include L2 and L1 layer communication links (e.g.,wired or wireless) with the MME/AMF to exchange information.

In some examples, a user plane protocol stack may include, in order fromhighest layer to lowest layer, SDAP 847, PDCP 840, RLC 830, MAC 820, andPHY 810. The user plane protocol stack may be used for communicationbetween the UE 101, the RAN node 111, and UPF 302 in NR implementationsor an S-GW 222 and P-GW 223 in LTE implementations. In this example,upper layers 851 may be built on top of the SDAP 847, and may include auser datagram protocol (UDP) and IP security layer (UDP/IP) 852, aGeneral Packet Radio Service (GPRS) Tunneling Protocol for the userplane layer (GTP-U) 853, and a User Plane PDU layer (UP PDU) 863.

The transport network layer 854 (also referred to as a “transportlayer”) may be built on IP transport, and the GTP-U 853 may be used ontop of the UDP/IP layer 852 (comprising a UDP layer and IP layer) tocarry user plane PDUs (UP-PDUs). The IP layer (also referred to as the“Internet layer”) may be used to perform packet addressing and routingfunctionality. The IP layer may assign IP addresses to user data packetsin any of IPv4, IPv6, or PPP formats, for example.

The GTP-U 853 may be used for carrying user data within the GPRS corenetwork and between the radio access network and the core network. Theuser data transported can be packets in any of IPv4, IPv6, or PPPformats, for example. The UDP/IP 852 may provide checksums for dataintegrity, port numbers for addressing different functions at the sourceand destination, and encryption and authentication on the selected dataflows. The RAN node 111 and the S-GW 222 may utilize an S1-U interfaceto exchange user plane data using a protocol stack comprising an L1layer (e.g., PHY 810), an L2 layer (e.g., MAC 820, RLC 830, PDCP 840,and/or SDAP 847), the UDP/IP layer 852, and the GTP-U 853. The S-GW 222and the P-GW 223 may utilize an S5/S8a interface to exchange user planedata using a protocol stack comprising an L1 layer, an L2 layer, theUDP/IP layer 852, and the GTP-U 853. As discussed previously, NASprotocols may support the mobility of the UE 101 and the sessionmanagement procedures to establish and maintain IP connectivity betweenthe UE 101 and the P-GW 223.

Moreover, although not shown by FIG. 8 , an application layer may bepresent above the AP 863 and/or the transport network layer 854. Theapplication layer may be a layer in which a user of the UE 101, RAN node111, or other network element interacts with software applications beingexecuted, for example, by application circuitry 405 or applicationcircuitry 505, respectively. The application layer may also provide oneor more interfaces for software applications to interact withcommunications systems of the UE 101 or RAN node 111, such as thebaseband circuitry 610. In some examples, the IP layer or theapplication layer, or both, may provide the same or similarfunctionality as layers 5-7, or portions thereof, of the Open SystemsInterconnection (OSI) model (e.g., OSI Layer 7—the application layer,OSI Layer 6—the presentation layer, and OSI Layer 5—the session layer).

FIG. 9 illustrates components of a core network 220. The components ofthe CN 220 may be implemented in one physical node or separate physicalnodes and may include components to read and execute instructions from amachine-readable or computer-readable medium (e.g., a non-transitorymachine-readable storage medium). In some examples, the components of CN320 may be implemented in a same or similar manner as discussed hereinwith regard to the components of CN 220. In some examples, NFV isutilized to virtualize any or all of the above-described network nodefunctions using executable instructions stored in one or morecomputer-readable storage mediums, as described in further detail below.A logical instantiation of the CN 220 may be referred to as a networkslice 901, and individual logical instantiations of the CN 220 mayprovide specific network capabilities and network characteristics. Alogical instantiation of a portion of the CN 220 may be referred to as anetwork sub-slice 902 (e.g., the network sub-slice 902 is shown toinclude the P-GW 223 and the PCRF 226).

As used herein, the terms “instantiate,” “instantiation,” and the likemay refer to the creation of an instance, and an “instance” may refer toa concrete occurrence of an object, which may occur, for example, duringexecution of program code. A network instance may refer to informationidentifying a domain, which may be used for traffic detection androuting in case of different IP domains or overlapping IP addresses. Anetwork slice instance may refer to a set of network functions (NFs)instances and the resources (e.g., compute, storage, and networkingresources) required to deploy the network slice.

With respect to 5G systems (see, e.g., FIG. 3 ), a network slice mayinclude a RAN part and a CN part. The support of network slicing relieson the principle that traffic for different slices is handled bydifferent PDU sessions. The network can realize the different networkslices by scheduling or by providing different L1/L2 configurations, orboth. The UE 301 provides assistance information for network sliceselection in an appropriate RRC message if it has been provided by NAS.While the network can support large number of slices, the UE need notsupport more than 8 slices simultaneously in some examples.

A network slice may include the CN 320 control plane and user plane NFs,NG-RANs 310 in a serving PLMN, and a N3IWF functions in the servingPLMN. Individual network slices may have different S-NSSAI or differentSSTs, or both. NSSAI includes one or more S-NSSAIs, and each networkslice is uniquely identified by an S-NSSAI. Network slices may differfor supported features and network functions optimizations. In someexamples, multiple network slice instances may deliver the same servicesor features but for different groups of UEs 301 (e.g., enterpriseusers). For example, individual network slices may deliver differentcommitted service(s) or may be dedicated to a particular customer orenterprise, or both. In this example, each network slice may havedifferent S-NSSAIs with the same SST but with different slicedifferentiators. Additionally, a single UE may be served with one ormore network slice instances simultaneously using a 5G AN, and the UEmay be associated with eight different S-NSSAIs. Moreover, an AMF 321instance serving an individual UE 301 may belong to each of the networkslice instances serving that UE.

Network slicing in the NG-RAN 310 involves RAN slice awareness. RANslice awareness includes differentiated handling of traffic fordifferent network slices, which have been pre-configured. Sliceawareness in the NG-RAN 310 is introduced at the PDU session level byindicating the S-NSSAI corresponding to a PDU session in all signalingthat includes PDU session resource information. How the NG-RAN 310supports the slice enabling in terms of NG-RAN functions (e.g., the setof network functions that comprise each slice) is implementationdependent. The NG-RAN 310 selects the RAN part of the network sliceusing assistance information provided by the UE 301 or the 5GC 320,which unambiguously identifies one or more of the pre-configured networkslices in the PLMN. The NG-RAN 310 also supports resource management andpolicy enforcement between slices as per SLAs. A single NG-RAN node maysupport multiple slices, and the NG-RAN 310 may also apply anappropriate RRM policy for the SLA in place to each supported slice. TheNG-RAN 310 may also support QoS differentiation within a slice.

The NG-RAN 310 may also use the UE assistance information for theselection of an AMF 321 during an initial attach, if available. TheNG-RAN 310 uses the assistance information for routing the initial NASto an AMF 321. If the NG-RAN 310 is unable to select an AMF 321 usingthe assistance information, or the UE 301 does not provide any suchinformation, the NG-RAN 310 sends the NAS signaling to a default AMF321, which may be among a pool of AMFs 321. For subsequent accesses, theUE 301 provides a temp ID, which is assigned to the UE 301 by the 5GC320, to enable the NG-RAN 310 to route the NAS message to theappropriate AMF 321 as long as the temp ID is valid. The NG-RAN 310 isaware of, and can reach, the AMF 321 that is associated with the tempID. Otherwise, the method for initial attach applies.

The NG-RAN 310 supports resource isolation between slices. NG-RAN 310resource isolation may be achieved by means of RRM policies andprotection mechanisms that should avoid that shortage of sharedresources if one slice breaks the service level agreement for anotherslice. In some examples, it is possible to fully dedicate NG-RAN 310resources to a certain slice. How NG-RAN 310 supports resource isolationis implementation dependent.

Some slices may be available only in part of the network. Awareness inthe NG-RAN 310 of the slices supported in the cells of its neighbors maybe beneficial for inter-frequency mobility in connected mode. The sliceavailability may not change within the UE's registration area. TheNG-RAN 310 and the 5GC 320 are responsible to handle a service requestfor a slice that may or may not be available in a given area. Admissionor rejection of access to a slice may depend on factors such as supportfor the slice, availability of resources, support of the requestedservice by NG-RAN 310.

The UE 301 may be associated with multiple network slicessimultaneously. In case the UE 301 is associated with multiple slicessimultaneously, only one signaling connection is maintained, and forintra-frequency cell reselection, the UE 301 tries to camp on the bestcell. For inter-frequency cell reselection, dedicated priorities can beused to control the frequency on which the UE 301 camps. The 5GC 320 isto validate that the UE 301 has the rights to access a network slice.Prior to receiving an Initial Context Setup Request message, the NG-RAN310 may be allowed to apply some provisional or local policies based onawareness of a particular slice that the UE 301 is requesting to access.During the initial context setup, the NG-RAN 310 is informed of theslice for which resources are being requested.

NFV architectures and infrastructures may be used to virtualize one ormore NFs, alternatively performed by proprietary hardware, onto physicalresources comprising a combination of industry-standard server hardware,storage hardware, or switches. In other words, NFV systems can be usedto execute virtual or reconfigurable implementations of one or more EPCcomponents and functions.

FIG. 10 depicts an example management system 1000 for mobile networksthat include virtualized network functions. The management system 1000can include a 3GPP management system 1002 and NFV-MANO framework 1004(e.g., ETSI GS NFV-MAN 001). The 3GPP management system 1002 of FIG. 10is based on 4G networks, but aspects of the management system may beapplicable to 5G networks or other networks. The architecture 1000 isillustrated as including a virtualized infrastructure manager (VIM)1006, a network function virtualization infrastructure (NFVI) 1008,virtualized network function(s) (VNFs) 1010, a VNF manager (VNFM) 1012,element managers (EMs) 1014, a network function virtualizationorchestrator (NFVO) 1016, and a network manager (NM) 1018. The mobilenetwork comprises physical and virtualized network elements.Application-specific aspects of both VNFs and PNFs, corresponding tophysical network elements (NEs), are managed by the 3GPP managementsystem 1002.

In the system 1000, the Itf-N is an interface between the NM 1018 andthe DM/EM 1014, the Os-Ma-nfvo is the reference point between theoperation support system (OSS)/business support system (BSS) (e.g., theNM 1014) and the NFVO 1016, the Ve-Vnfm-em is the reference pointbetween the EM 1014 and the VNFM 1012, and the Ve-Vnfm-vnf is thereference point between the VNF 1010 and the VNFM 1012.

The NFVI 1008 comprises hardware and software components that togetherprovide the infrastructure resources where VNFs are deployed. Theinfrastructure resources contain the hardware resources, virtualizationlayer software and the virtualized resources which the VNF relies on.NFVI resources under consideration are both virtualized andnon-virtualized resources, supporting virtualized network functions andpartially virtualized network functions. Virtualized resources includethose that can be associated with virtualization containers, and havebeen cataloged and offered for consumption through appropriatelyabstracted services, for example, compute including machines (e.g.,hosts or bare metal), and virtual machines, as resources that compriseboth CPU and memory; storage, including: volumes of storage at eitherblock or file-system level; and network, including: networks, subnets,ports, addresses, links and forwarding rules, for the purpose ofensuring intra- and inter-VNF connectivity.

The EMs 1014 track the performance, fault and security of the functionalaspects of VNFs 1010. The tracking data from the VNFM 1012 and the EMs1014 may comprise, for example, performance management (PM) data used bythe VIM or the NFVI 1008. Both the VNFM 1012 and the EM 1014 can scaleup/down the quantity of VNFs 1010 of the system 1000.

The NM 1018 supports the OSS/BSS and is the consumer of reference pointOs-Ma-nfvo. The NM 1018 provides the functions for management of mobilenetworks, including the VNFs 1010. The NM 1018 may provide a package ofend-user functions with the responsibility for the management of anetwork, which may include network elements with VNFs, non-virtualizednetwork functions, or both (management of the VNFs may occur via an EM).The NM 1018 can support fault, configuration, accounting, performance,and security (FCAPS) management functions of the mobile network (e.g.IMS, EPC, NR, etc.) and 3GPP service (e.g. data service, voice service)and supports the management of mobile network lifecycle. NM 1018initiates the lifecycle management of NS and VNF, which are related tomobile network, through interaction with NFV-MANO 1004.

The EM 1014 and/or DM is responsible for FCAPS management functionalityfor a VNF 1010 on an application level and physical NE on a domain andelement level. This includes: fault management for VNF and physical NE;configuration management for VNF and physical NE; accounting managementfor VNF and physical NE; performance measurement and collection for VNFand physical NE; and security management for VNF and physical NE. EM/DMparticipates in lifecycle management functionality for a VNF, such as byrequesting a lifecycle management operation for a VNF to VNFM, andexchanging information regarding the VNF and Virtualized Resourcesassociated with the VNF. The DM/EM (including EM extended functionality)can manage both PNF(s) and VNF(s).

The NFV-MANO 1004 comprises the NFVO 1016, VNFM 1012, and VIM 1006. TheNFVO 1016 and VNFM 1012 share interfaces with the NM 1018, DM/EM 1014and VNF 1010. The NFVO 1016 is responsible for the orchestration of NFVIresources across multiple VIMs 1006, fulfilling the ResourceOrchestration functions, and the lifecycle management of NetworkServices, fulfilling the Network Service Orchestration functions. TheNFVO 1016 may coordinate, authorize, release and engage resources of theNFVI in order to provide the requested service (e.g., to execute anetwork function, component, or slice).

The VIM 1006 manages the resources of the NFVI 1008. The NFVI 1008 caninclude physical or virtual resources and applications (includinghypervisors) used to execute the system 1000. The VIM 1006 may managethe life cycle of virtual resources with the NFVI 1008 (e.g., creation,maintenance, and tear down of VMs associated with one or more physicalresources), track VM instances, track performance, fault and security ofVM instances and associated physical resources, and expose VM instancesand associated physical resources to other management systems.

The VNFM 1012 manages the VNFs 1010. The VNFs 1010 may be used toexecute network (e.g., EPC, NR, etc.) components/functions. The VNFM1012 may manage the life cycle of the VNFs 1010 and track performance,fault and security of the virtual aspects of VNFs 1010.

The management and orchestration of virtualized resources includeshanding NFVI resources (e.g. in NFVI Nodes), in NFVI Points of Presence(NFVI-PoPs). Management of non-virtualized resources is restricted toprovisioning connectivity to PNFs, necessary when a NS instance includesa PNF that needs to connect to a VNF, or when the NS instance isdistributed across multiple NFVI-PoPs or N-PoPs.

The virtualized resources are leveraged for providing the VNFs 1010 withthe resources they need. Resource allocation in the NFVI 1008 is apotentially complex task because a lot of requirements and constraintsmay need to be met at the same time. In particular, requirements fornetwork allocation add new complexity compared to known resourceallocation strategies for computing resources in virtualizedenvironments. For example, some VNFs 1010 require low latency or highbandwidth links to other communication endpoints.

Allocation and release of resources is a dynamic process, in response toconsumption of those services by other functions. While the managementand orchestrations function for virtualized infrastructure areVNF-unaware, resource allocations and releases may be needed throughoutthe VNF lifetime. An advantage of NFV is that with increasing load VNFscan dynamically consume services that allocate additional resource whenscaling-out is triggered.

Services exposing virtualized resources include, but are not limited to:discovery of available services; management of virtualized resourcesavailability/allocation/release; and virtualized resourcefault/performance management.

In the case of virtualized resources distributed across multipleNFVI-PoPs, those services could either be exposed directly by themanagement and orchestration functions for each individual NFVI-PoP, orvia a higher-level service abstraction presenting the virtualizedresources across multiple NFVI-PoPs. Both types of services could beexposed to the consuming functions. In the case of the higher levelservice abstraction previously mentioned, the management andorchestration of virtualized resources and non-virtualised networkingresources across those NFVI-PoPs falls under the responsibility of themanagement and orchestration of the virtualized infrastructure that mayin turn use the services exposed directly by the management andorchestration functions of a single or across multiple NFVI-PoPs. Inorder to provide those services, the management and orchestration of thevirtualized infrastructure consumes services provided by the NFVI.

The NFV management and orchestration functions that coordinatevirtualized resources in a single NFVI-PoP and/or across multipleNFVI-PoPs should ensure exposure of services that support accessingthese resources in an open, abstracted manner. These services can beconsumed by other authenticated and properly authorized NFV managementand orchestration functions (e.g. functions that manage and orchestratevirtualized network functions).

Network Service Lifecycle management includes, among other things,on-boarding Network Service (e.g., registering a Network Service in thecatalogue and ensure that all the templates describing the NS areon-boarded); instantiating a Network Service (e.g., creating a NetworkService using the NS on-boarding artefacts); scaling a Network Service(e.g., increasing or reducing the capacity of the Network Service);updating a Network Service by supporting Network Service configurationchanges of various complexity such as changing inter-VNF connectivity orthe constituent VNF instances; performing create, delete, query, andupdate procedures for VNF forwarding graphs (VNFFGs) associated to aNetwork Service; and terminating Network Services (e.g., requesting thetermination of constituent VNF instances, requesting the release of NFVIresources associated to NSs, and return them to NFVI resource pool, ifapplicable.

The deployment and operational behavior requirements of each NetworkService can be captured in a deployment template, and stored during theNetwork Service on-boarding process in a catalogue, for future selectionfor instantiation. The deployment template describes the attributes andrequirements used to realize such a Network Service. Network ServiceOrchestration coordinates the lifecycle of VNFs that jointly realize aNetwork Service. In some examples, this includes managing theassociations between different VNFs, and when applicable between VNFsand PNFs, the topology of the Network Service, and the VNFFGs associatedwith the Network Service.

During the Network Service lifecycle, the Network Service Orchestrationfunctions may monitor key performance indicators (KPIs) of a NetworkService if such requirements were captured in the deployment template,and may report this information to support explicit request for suchoperations from other functions.

The Network Service Orchestration performs its services by using the VNFmanagement functions and by orchestrating the NFV Infrastructure thatsupports the interconnection between VNFs functionality, and itsfunctions are exposed in an open, abstracted manner as services to otherfunctions. In order to fulfil its responsibilities, the Network ServiceOrchestration functions consume services exposed by other functions(e.g., Virtualized Infrastructure management functions).

In some examples, the services provided by Network Service Orchestrationcan be consumed by other functions that are authenticated and authorized(e.g. OSS, BSS).

The VNFM 1012 is responsible for the lifecycle management of VNFinstances. Each VNF instance is assumed to have an associated VNFManager. The VNF manager may be assigned the management of a single VNFinstance, or the management of multiple VNF instances of the same typeor of different types.

In some examples, the VNFM functions are assumed to be generic functionsapplicable to multiple VNFs. The NFV-MANO architectural framework mayalso support cases where VNF instances need specific functionality fortheir lifecycle management, and such functionality may be specified inthe VNF Package.

The VNF 1010 is configured to perform VNF instantiation, including VNFconfiguration if required by the VNF deployment template (e.g., VNFinitial configuration with IP addresses before completion of the VNFinstantiation operation); VNF instantiation feasibility checking; VNFinstance software update/upgrade; VNF instance modification; VNFinstance scaling out/in and up/down; VNF instance-related collection ofNFVI performance measurement results and faults/events information, andcorrelation to VNF instance-related events/faults; VNF instance assistedor automated healing; VNF instance termination; VNF lifecycle managementchange notification; management of the integrity of the VNF instancethrough its lifecycle; and overall coordination and adaptation role forconfiguration and event reporting between the VIM and the EM. Theaforementioned functionalities may be exposed by means of interfaces andconsumed by other NFV-MANO functional blocks or by authorized externalentities.

The deployment and operational behavior of each VNF 1010 can be capturedin a template (e.g., a Virtualized Network Function Descriptor (VNFD))that is stored in the VNF catalogue. NFV-MANO uses a VNFD to createinstances of the VNF it represents, and to manage the lifecycle of thoseinstances. A VNFD has a one-to-one correspondence with a VNF Package,and describes the attributes and requirements to realize such a VNF.NFVI resources are assigned to a VNF based on the requirements capturedin the VNFD (containing resource allocation criteria, among others), butalso taking into consideration specific requirements, constraints, andpolicies that have been pre-provisioned or are accompanying the requestfor instantiation and may override certain requirements in the VNFD(e.g., operator policies, geo-location placement, affinity/anti-affinityrules, local regulations).

The information elements to be handled by the NFV-MANO 1004, includingthe VNFD among others, may guarantee the flexible deployment andportability of VNF instances on multi-vendor and diverse NFVIenvironments (e.g., with diverse computing resource generations, diversevirtual network technologies, etc.). To do so, hardware resources areabstracted and the VNF requirements are described in terms of suchabstraction.

The VNFM 1012 has access to a repository of available VNF Packages anddifferent versions of them, all represented via their associated VNFDs.Different versions of a VNF Package may correspond to differentimplementations of the same function, different versions to run indifferent execution environments (e.g., on different hypervisors,dependent on NFVI resources availability information, etc.), ordifferent release versions of the same software. The repository may bemaintained by the NFVO or another external entity.

The VIM 1006 is responsible for controlling and managing the NFVIcompute, storage and network resources, usually within an operator'sInfrastructure Domain (e.g., all resources within an NFVI-PoP, resourcesacross multiple NFVI-POPs, or a subset of resources within an NFVI-PoP)as discussed previously. A VIM 1006 may be specialized in handling acertain type of NFVI resource (e.g., compute-only, storage-only,networking-only, etc.), or may be capable of managing multiple types ofNFVI resources (e.g. in NFVI-Nodes). A particular example of aspecialized VIM is a WAN Infrastructure Manager (WIM), which is used toestablish connectivity between PNF endpoints in different NFVI-PoPs.

In some examples, the VIM 1006 is configured to: orchestrate theallocation/upgrade/release/reclamation of NFVI resources (which mayinclude the optimization of such resources usage), and manage theassociation of the virtualized resources to the physical compute,storage, networking resources, wherein the VIM keeps an inventory of theallocation of virtual resources to physical resources (e.g., to a serverpool and/or the like). The VIM also supports the management of VNFForwarding Graphs (create, query, update, delete), for example, bycreating and maintaining Virtual Links, virtual networks, sub-nets, andports, as well as the management of security group policies to ensurenetwork/traffic access control.

The VIM 1006 can also manage, in a repository, inventory relatedinformation of NFVI hardware resources (compute, storage, networking)and software resources (e.g., hypervisors), and discovery of thecapabilities and features (e.g., related to usage optimization) of suchresources; manage the virtualized resource capacity (e.g., density ofvirtualized resources to physical resources), and forwarding ofinformation related to NFVI resources capacity and usage reporting;manage software images (add, delete, update, query, copy) as requestedby other NFV-MANO functional blocks (e.g., NFVO). The VIM can maintainrepositories for software images, in order to streamline the allocationof virtualized computing resources, and a validation step, performed byVIM, is required for software images before storing the image (e.g., VNFpackage on-boarding and update).

The VIM 1006 can collect performance and fault information (e.g., vianotifications) of hardware resources (compute, storage, and networking)software resources (e.g., hypervisors), and virtualized resources (e.g.,VMs); and forwarding of performance measurement results andfaults/events information relative to virtualized resources; and

In some examples, the VIM 1006 manages catalogues of virtualizedresources that can be consumed from or by the NFVI 1008. The elements inthe catalogue may be in the form of virtualized resource configurations(virtual CPU configurations, types of network connectivity (e.g., L2,L3), etc.), and/or templates (e.g., a virtual machine with two virtualCPUs and two GB of virtual memory).

FIG. 11 is a block diagram illustrating components for readinginstructions from a machine-readable or computer-readable medium (e.g.,a non-transitory machine-readable storage medium) and performing any oneor more of the techniques described herein. Specifically, FIG. 11 showsa diagrammatic representation of hardware resources 1100 including oneor more processors (or processor cores) 1110, one or more memory orstorage devices 1120, and one or more communication resources 1130, eachof which may be communicatively coupled using a bus 1140. Forimplementations where node virtualization (e.g., NFV) is utilized, ahypervisor 1102 may be executed to provide an execution environment forone or more network slices or sub-slices to utilize the hardwareresources 1100.

The processors 1110 may include a processor 1112 and a processor 1114.The processor(s) 1110 may be, for example, a central processing unit(CPU), a reduced instruction set computing (RISC) processor, a complexinstruction set computing (CISC) processor, a graphics processing unit(GPU), a DSP such as a baseband processor, an ASIC, an FPGA, aradio-frequency integrated circuit (RFIC), another processor (includingthose discussed herein), or any suitable combination thereof.

The memory/storage devices 1120 may include main memory, disk storage,or any suitable combination thereof. The memory/storage devices 1120 mayinclude, but are not limited to, any type of volatile or nonvolatilememory such as dynamic random access memory (DRAM), static random accessmemory (SRAM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), Flashmemory, or solid-state storage, or combinations of them, among others.

The communication resources 1130 may include interconnection or networkinterface components or other suitable devices to communicate with oneor more peripheral devices 1104 or one or more databases 1106 using anetwork 1108. For example, the communication resources 1130 may includewired communication components (e.g., for coupling using USB), cellularcommunication components, NFC components, Bluetooth® (or Bluetooth® LowEnergy) components, Wi-Fi® components, and other communicationcomponents.

Instructions 1150 may comprise software, a program, an application, anapplet, an app, or other executable code for causing at least any of theprocessors 1110 to perform any one or more of the methodologiesdiscussed herein. The instructions 1150 may reside, completely orpartially, within at least one of the processors 1110 (e.g., within theprocessor's cache memory), the memory/storage devices 1120, or anysuitable combination thereof. Furthermore, any portion of theinstructions 1150 may be transferred to the hardware resources 1100 fromany combination of the peripheral devices 1104 or the databases 1106.Accordingly, the memory of processors 1110, the memory/storage devices1120, the peripheral devices 1104, and the databases 1106 are examplesof computer-readable and machine-readable media.

When an AF (e.g., AF 328) needs to trigger a UE (e.g., UE 101, 201, 301)to perform some action, the AF requests the NEF (e.g., NEF 323) to sendan application trigger to the UE. To do so, the AF can invoke theNnef_Trigger service to request that the network send an applicationtrigger to the UE.

FIG. 12 shows an example device triggering procedure 1200 according tosome embodiments. The device triggering procedure 1200 may operate asfollows:

1. The AF determines the need to trigger the device (e.g., the UE). Ifthe AF has no contact details for the NEF, it can discover and selectthe NEF services, as described in 3GPP TS 23.502.

2. The AF communicates with the NEF to invoke the Nnef_Trigger_Deliveryservice operation to request that an application trigger be sent to aUE, and to subscribe to notifications about the result of theapplication trigger delivery attempt. Additional details on theNnef_Trigger_Delivery service operation are described in clause5.2.6.5.2 of 3GPP TS 23.502.

3. The NEF checks that the AF is authorized to send trigger requests andthat the AF has not exceeded its quota or rate of trigger submissionover Nnef. If this check fails, the NEF sends a Nnef_Trigger_Deliveryresponse to the AF with a cause value indicating the reason for thefailure condition and the flow stops at this step. Otherwise, the flowcontinues with step 4 of the procedure 1200.

4. When the AF is authorized to trigger the UE, the NEF invokes theNudm_SDM_Get service operation (e.g., with Identifier Translation, GPSIand AF Identifier as parameters) to resolve the Generic PublicSubscription Identifier (GPSI) to a Subscription Permanent Identifier(SUPI). In some examples, mapping from GPSI (External Id) to GPSI(mobile subscription ISDN number (MSISDN)) is provided to supportinfrastructure without MSISDN-less SMS capabilities. Additional detailson the Nudm_SDM_Get service operation are described in clause 5.2.3.3.1of 3GPP TS 23.502.

5. The UDM may invoke the Nudr_DM_Query service operation to retrieve alist of AFs that are allowed to trigger the UE and determines, based onUDM policy, which identifier (e.g., SUPI or MSISDN) should be used totrigger the UE. Additional details on the Nudr_DM_Query serviceoperation are described in clause 5.2.12.2.2 of 3GPP TS 23.502. If theAF is authorized to trigger the UE, the UDM provides a Nudm_SDM_Getresponse with the appropriate identifier (e.g., with the SUPI or MSISDN,or both). If the AF is not allowed to send a trigger message to the UE,or there is no valid subscription information for the UE, the NEF sendsa Nnef_Trigger_Delivery response with a cause value indicating thereason for the failure condition and the flow stops at this step.Otherwise, the flow continues with step 6. In some examples, thepresence of an MSISDN in the reply is interpreted as an indication tothe NEF that MSISDN is used (instead of IMSI) to identify the UE whensending the SMS to the SMS Service Center (SMS-SC) via T4.

6. The NEF invokes the Nudm_UECM_Get service operation (e.g., with SUPI,SMS) to retrieve the UE SMSF identities. Additional details on theNudm_UECM_Get service operation are described in clause 5.2.3.2.4 of3GPP TS 23.502.

7. The UDM may invoke the Nudr_DM_Query service to retrieve the UE SMSFidentities. The UDM provides a Nudm_UECM_Get response with thecorresponding UE SMSF identities. UDM policy (which may be dependent onthe Visited Public Land Mobile Network (VPLMN) ID) may influence whichserving node identities are returned. In some examples, the NEF cancache serving node information for the UE. However, this can increasethe probability of trigger delivery attempt failures when the cachedserving node information is stale.

8. The NEF selects a suitable SMS-SC based on configured information. Insome examples, the NEF acts as a Machine Type CommunicationsInterworking Function (MTC-IWF) and sends a Submit Trigger (e.g., withthe GPSI, SUPI, AF Identifier, trigger reference number, validityperiod, priority, SMSF serving node ID(s) (if available, are obtainedfrom UDM in step 7), SMS Application port ID, trigger payload, TriggerIndication) message to the SMS-SC. If the NEF indicates that “Absentsubscriber” was received from the UDM, the SMS-SC should not submit themessage, but store it directly and send Routing Information for SM torequest the UDM to add the SMS-SC address to the Message Waiting List.

9. The SMS-SC sends a Submit Trigger Confirm message to the NEF toconfirm that the submission of the SMS has been accepted by the SMS-SC.

10. The NEF sends a Nnef_Trigger_Delivery response to the AF to indicateif the Device Trigger Request has been accepted for delivery to the UE.

11. The SMS-SC performs Mobile Terminated (MT) SMS delivery (e.g., asdefined in clause 4.13.3 of 3GPP TS 23.502). The SMS-SC may provide therouting information that it received in step 6 to the SMS Gateway MobileServices Switching Center (GMSC) to avoid UDM interrogation. The SMS-SCgenerates the necessary Call Detail Record (CDR) information andincludes the AF Identifier. The SMS Application port ID, which isincluded in the SM User Data Header, and the Trigger Indication areincluded in the CDRs in order to enable differentiated charging. TheSMS-SC stores the trigger payload, without routing information. If themessage delivery fails and is attempted to be delivered again, UDMinterrogation will be performed. If the message delivery fails and thevalidity period of this trigger message is not set to zero, the SMS-SCshall send a SM Message Delivery Status Report to request the UDM to addthe SMS-SC address to the Message Waiting list. When the messagedelivery is later re-attempted, a new UDM interrogation will beperformed by the SMS-GMSC using SUPI or MSISDN. UDM interrogations usingSUPI may not be forwarded or relayed to SMS-Router or IP-SM-GWs. The UDMmay include up to four serving node identities (MSC or MME, SGSN,IP-SM-GW, AMF) in the response to SMS-GMSC.

12. If the message delivery fails (either directly or when validityperiod of the trigger message expires) or when the message deliverysucceeds, the SMS-SC may send a Message Delivery Report (e.g., with thecause code, trigger reference number, AF Identifier) to the NEF.

13. The NEF provides a Nnef_Trigger_Delivery Notify message to the AFwith a Delivery Report indicating the trigger delivery outcome (e.g.succeeded, unknown or failed and the reason for the failure). Additionaldetails on the Nnef_Trigger_Delivery Notify operation are described inclause 5.2.6.5.3 of 3GPP TS 23.502. The NEF generates the CDRinformation including the GPSI and AF Identifier.

14. In response to the received device trigger, the UE takes specificactions and may take into consideration the content of the triggerpayload. This action typically involves initiation of immediate or latercommunication with the AF.

The application in the UE may perform actions as indicated by thetrigger payload when the trigger payload is received at the UE. Forexample, the UE may initiate immediate or later communication with theapplication server based on the information contained in the triggerpayload, which may include the PDU Session Establishment procedure ifthe related PDU Session is not already established. Thus, in order toensure that the application runs normally, the network needs tosuccessfully deliver the application trigger to the UE.

The SMS can be transferred over the non-access stratum (NAS) in 5Gnetworks. To enable SMS over NAS transporting, the UE includes a “SMSsupported” indication in its registration request indicating the UE'scapability for SMS over NAS transport. In response, the networkindicates to the UE whether the network allows the SMS message deliveryover NAS in the registration accept message. If the SMS over NAS isallowed by the network, then the SMS messages can originate at the UE(e.g., for mobile originated (MO) messages) or be terminated by the UE(e.g., for mobile terminated (MT) messages), via 3GPP or non-3GPP access(see e.g., clause 4.13.3 of 3GPP TS 23.502). The performance of SMS overNAS, as a service provided to the end users, should be monitored.

FIG. 13 shows an example non-roaming architecture 1300 to support SMSover NAS using the service-based interfaces within the control plane. Inthe non-roaming architecture 1300, the SMS Function (SMSF) may beconnected to the SMS-GMSC/IWMSC/SMS Router using, for example, one ofthe standardized interfaces as shown in 3GPP TS 23.203. In someexamples, SMSF re-allocation while the UE is in RM REGISTERED state isnot supported. Thus, when the serving AMF is re-allocated for a givenUE, the source AMF includes the SMSF identifier as part of UE contexttransfer to the target AMF. The UDM may be connected to theSMS-GMSC/IWMSC/SMS Router using, for example, one of the standardizedinterfaces as shown in 3GPP TS 23.203. In some examples, each UE isassociated with only one SMSF in the registered PLMN. To support MT SMSdomain selection by the IP-SM-GW/SMS Router, the IP-SM-GW/SMS Router mayconnect to SGs MSC, MME or SMSF, or combinations of them, using, forexample, one of the standardized interfaces as shown in 3GPP TS 23.203.

The present disclosure provides techniques for generating performancemeasurements related to application triggering for NEF and performancemeasurements related to SMS over NAS for AMF. The performancemeasurements related to application triggering for NEF provides theinformation for monitoring the performance of the triggering, andperformance measurements related to SMS over NAS for AMF indicate theperformance on providing the SMS over NAS to the end users.

FIG. 14 illustrates an example performance measurement system 1400. Inthe system 1400, a service producer 1402 (which may include softwareand/or hardware components) collects raw performance measurements fromone or more NFs 1404. The service provider 1402 (or another entity) thenuses the raw performance measurements to generate or derive performancedata (sometimes referred to here as “performance indicators”) for theone or more NFs 1404. The performance data can then be provided to, forexample, service consumers.

In some examples, one or more of the NFs 1404 may be part of a group orset of NFs. The performance measurements for the group or set of NFs maybe aggregated (e.g., according to an aggregation method identified in aperformance indicator definition) and used to derive performanceindicators for the group or set of NFs.

In general, performance indicators are derived from the performancemeasurements aggregated over one or more NFs, such as, for example,average latency along the network slice instance (NSI). The performanceindicators can be derived from the performance measurements collected atthe NF or the NFs that belong to the group. In some examples, theaggregation method is identified in the performance indicatordefinition. Performance indicators at the network slice subset instance(NSSI) level can be derived from the performance measurements collectedat the NF(s) that belong to the NSSI or to constituent NSSIs. Theperformance indicators at the NSSI level can be made available using,for example, the corresponding performance management service for NSSI.In some examples, the performance indicators at the NSI level can bederived from the NSSI level performance indicators collected at theconstituent NSSIs and/or NFs. The NSI level performance indicators canbe made available using, for example, the corresponding performancemanagement service for NSI.

In some examples, the performance measurements related to applicationtriggering for NEF include a measurement of application triggerrequests. This measurement can provide the number of application triggerrequests received by the NEF from the AF. In some examples, thismeasurement is collected by a cumulative counter (e.g., an integervalue) that is updated in response to receipt of a Nnef_Trigger_Deliveryrequest by the NEF from the AF (see, e.g., 3GPP TS 23.502). In someexamples, the measurement type (e.g., as defined in 3GPP TS 32.404,incorporated herein by reference in its entirety) for this measurementis AT.AppTriggerReq. In some examples, the measurement object class(e.g., as defined in 3GPP TS 32.404) is NEFFuntion. This measurement canbe valid for packet switched traffic, and can be a pure 5G system (5GS)measurement (e.g., only 5GS events are counted).

In some examples, the performance measurements related to applicationtriggering for NEF include a measurement of application trigger requestsaccepted for delivery. This measurement can provide the number ofapplication trigger requests accepted for delivery to the UE. In someexamples, this measurement is collected by a cumulative counter (e.g.,an integer value) that is updated in response to transmission of aNnef_Trigger_Delivery response by the NEF to the AF indicating that theapplication trigger request has been accepted for delivery to the UE(see, e.g., 3GPP TS 23.502). In some examples, the measurement type(e.g., as defined in 3GPP TS 32.404) for this measurement isAT.AppTriggerAcc. In some examples, the measurement object class (e.g.,as defined in 3GPP TS 32.404) is NEFFuntion. This measurement can bevalid for packet switched traffic, and can be a pure 5GS measurement.

In some examples, the performance measurements related to applicationtriggering for NEF include a measurement of application trigger requestsrejected for delivery. This measurement can provide the number ofapplication trigger requests rejected for delivery to the UE. In someexamples, this measurement is collected by a cumulative counter (e.g.,an integer value) that is updated in response to transmission of aNnef_Trigger_Delivery response by the NEF to the AF indicating that theapplication trigger request has been rejected for delivery to the UE(see, e.g., 3GPP TS 23.502). In some examples, this measurement is splitinto sub-counters (each of which may be an integer value) per error code(e.g., response code), and each Nnef_Trigger_Delivery responseincrements the relevant sub-counter based on the error code. In someexamples, the measurement type (e.g., as defined in 3GPP TS 32.404) forthis measurement is AT.AppTriggerRej.ErrorCode. In some examples, themeasurement object class (e.g., as defined in 3GPP TS 32.404) isNEFFuntion. This measurement can be valid for packet switched traffic,and can be a pure 5GS measurement.

In some examples, the performance measurements related to applicationtriggering for NEF include a measurement of application trigger deliveryreports. This measurement can provide the number of application triggerdelivery reports indicating the delivery results (e.g., success orfailure) sent by the NEF to the AF. In some examples, this measurementis collected by a cumulative counter (e.g., an integer value) that isupdated in response to transmission of a Nnef_Trigger_Delivery Notifymessage by the NEF to the AF indicating the delivery result of theapplication trigger (see, e.g., 3GPP TS 23.502). In some examples, thismeasurement is split into sub-counters (each of which may be an integervalue) per delivery result, and each Nnef_Trigger_Delivery Notifymessage increments the relevant sub-counter based on the deliveryresult. In some examples, the measurement type (e.g., as defined in 3GPPTS 32.404) for this measurement is AT.AppTriggerRej.DeliveryResult. Insome examples, the measurement object class (e.g., as defined in 3GPP TS32.404) is NEFFuntion. This measurement can be valid for packet switchedtraffic, and can be a pure 5GS measurement.

The performance measurements can also include measurements related toSMS over NAS. In some examples, these measurements distinguish betweeninstances of 3GPP access (e.g., access in accordance with the 3GPPstandards) and non-3GPP access. In other examples, these measurementsare made without distinguishing between 3GPP and non-3GPP access.

In some examples, the performance measurements related to SMS over NASinclude a measurement of registration of SMS over NAS. This measurementcan provide the number of requests for registration of SMS over NASreceived by the AF from the UEs. In some examples, this measurement iscollected by a cumulative counter (e.g., an integer value) that isupdated in response to a registration request message containing the“SMS supported” indication indicating that the UE supports SMS deliveryover NAS by the AMF from the UE (see, e.g., 3GPP TS 23.502). In someexamples, this measurement is split into sub-counters (each of which maybe an integer value) based on the type of access (e.g., 3GPP or non-3GPPaccess), and each registration request message increments the relevantsub-counter based on the access type. In other examples, no distinctionis made between the types of access (e.g., all registration requestmessages increment a single counter). In some examples, the measurementtype (e.g., as defined in 3GPP TS 32.404) for this measurement isAT.SmsOverNasRegReq (or AT.SmsOverNasReg3GPPReq andAT.SmsOverNasRegNon3GPPReq if access distinctions are made). In someexamples, the measurement object class (e.g., as defined in 3GPP TS32.404) is AMFFuntion. This measurement can be valid for packet switchedtraffic, and can be a pure 5GS measurement.

In some examples, the performance measurements related to SMS over NASinclude a measurement of successful registrations of SMS over NAS. Thismeasurement can provide the number of successful registrations allowedfor SMS over NAS sent by the AF to the UEs. In some examples, thismeasurement is collected by a cumulative counter (e.g., an integervalue) that is updated in response to transmission of a registrationaccept message containing the “SMS allowed” indication by the AMF to theUE (see, e.g., 3GPP TS 23.502). In some examples, this measurement issplit into sub-counters (each of which may be an integer value) based onthe type of access (e.g., 3GPP or non-3GPP access), and eachregistration accept message increments the relevant sub-counter based onthe access type. In other examples, no distinction is made between thetypes of access (e.g., all registration accept messages increment asingle counter). In some examples, the measurement type (e.g., asdefined in 3GPP TS 32.404) for this measurement is AT.SmsOverNasRegSucc(or AT.SmsOverNasReg3GPPSucc and AT.SmsOverNasRegNon3GPPSucc if accessdistinctions are made). In some examples, the measurement object class(e.g., as defined in 3GPP TS 32.404) is AMFFuntion. This measurement canbe valid for packet switched traffic, and can be a pure 5GS measurement.

In some examples, the performance measurements related to SMS over NASinclude a measurement of attempted mobile originated (MO) SMS messagesover NAS. This measurement can provide the number of NAS messagesencapsulating SMS messages received by the AF from the UE(s). In someexamples, this measurement is collected by a cumulative counter (e.g.,an integer value) that is updated in response to receipt of a NASmessage with an indication of SMS transportation by the AMF from the UE(see, e.g., 3GPP TS 23.502). In some examples, this measurement is splitinto sub-counters (each of which may be an integer value) based on thetype of access used for the message (e.g., 3GPP or non-3GPP access), andeach message increments the relevant sub-counter based on the accesstype. In other examples, no distinction is made between the types ofaccess (e.g., all messages increment a single counter). In someexamples, the measurement type (e.g., as defined in 3GPP TS 32.404) forthis measurement is AT.SmsOverNasMoReq (or AT.SmsOverNasMo3GPPReq andAT.SmsOverNasRegMo3GPPReq if access distinctions are made). In someexamples, the measurement object class (e.g., as defined in 3GPP TS32.404) is AMFFuntion. This measurement can be valid for packet switchedtraffic, and can be a pure 5GS measurement.

In some examples, the performance measurements related to SMS over NASinclude a measurement of successful MO SMS messages over NAS. Thismeasurement can provide the number of MO SMS messages successfullytransported over NAS. In some examples, this measurement is collected bya cumulative counter (e.g., an integer value) that is updated inresponse to transmission by the AMF to the UE of a NAS message thatincludes a “submit report” indicating that the MO SMS message has beensuccessfully delivered (see, e.g., 3GPP TS 23.502). In some examples,this measurement is split into sub-counters (each of which may be aninteger value) based on the type of access used to transport the message(e.g., 3GPP or non-3GPP access), and each successful message incrementsthe relevant sub-counter based on the access type. In other examples, nodistinction is made between the types of access (e.g., all messagesincrement a single counter). In some examples, the measurement type(e.g., as defined in 3GPP TS 32.404) for this measurement isAT.SmsOverNasMoSucc (or AT.SmsOverNasMo3GPPSucc andAT.SmsOverNasRegMo3GPPSucc if access distinctions are made). In someexamples, the measurement object class (e.g., as defined in 3GPP TS32.404) is AMFFuntion. This measurement can be valid for packet switchedtraffic, and can be a pure 5GS measurement.

In some examples, the performance measurements related to SMS over NASinclude a measurement of attempted mobile terminated (MT) SMS messagesover NAS. This measurement can provide the number of NAS messagesencapsulating SMS messages sent by the AF to the UE(s). In someexamples, this measurement is collected by a cumulative counter (e.g.,an integer value) that is updated in response to transmission of a NASmessage with an indication of SMS transportation by the AMF to the UE(see, e.g., 3GPP TS 23.502). In some examples, this measurement is splitinto sub-counters (each of which may be an integer value) based on thetype of access used for the message (e.g., 3GPP or non-3GPP access), andeach message increments the relevant sub-counter based on the accesstype. In other examples, no distinction is made between the types ofaccess (e.g., all messages increment a single counter). In someexamples, the measurement type (e.g., as defined in 3GPP TS 32.404) forthis measurement is AT.SmsOverNasMtReq (or AT.SmsOverNasMt3GPPReq andAT.SmsOverNasRegMt3GPPReq if access distinctions are made). In someexamples, the measurement object class (e.g., as defined in 3GPP TS32.404) is AMFFuntion. This measurement can be valid for packet switchedtraffic, and can be a pure 5GS measurement.

In some examples, the performance measurements related to SMS over NASinclude a measurement of successful MT SMS messages over NAS. Thismeasurement can provide the number of MT SMS messages successfullytransported over NAS. In some examples, this measurement is collected bya cumulative counter (e.g., an integer value) that is updated inresponse to receipt, by the AMF and from the UE, of a NAS message thatincludes a “delivery report” indicating that the MT SMS message has beensuccessfully delivered (see, e.g., 3GPP TS 23.502). In some examples,this measurement is split into sub-counters (each of which may be aninteger value) based on the type of access used to transport the message(e.g., 3GPP or non-3GPP access), and each successful message incrementsthe relevant sub-counter based on the access type. In other examples, nodistinction is made between the types of access (e.g., all messagesincrement a single counter). In some examples, the measurement type(e.g., as defined in 3GPP TS 32.404) for this measurement isAT.SmsOverNasMtSucc (or AT.SmsOverNasMt3GPPSucc andAT.SmsOverNasRegMt3GPPSucc if access distinctions are made). In someexamples, the measurement object class (e.g., as defined in 3GPP TS32.404) is AMFFuntion. This measurement can be valid for packet switchedtraffic, and can be a pure 5GS measurement.

FIG. 15 illustrates a flowchart of an example process 1500 forperformance measurements related to application triggering and SMS overNAS. In some examples, the electronic device(s), network(s), system(s),chip(s) or component(s), or portions or implementations thereof, ofFIGS. 1-14 may be configured to perform the process 1500.

Operations of the process 1500 include obtaining raw performancemeasurements from one or more network functions in a wirelesscommunication network (1502). The one or more network functions includeat least one of a network exposure function (NEF) or an access andmobility management function (AMF). The raw performance metrics can beobtained, for example, by a core network (e.g., a core network 120, 220,320, such as a 5G core network) or another component of the wirelesscommunication system 100.

Performance measurements (or performance indicators) for the one or morenetwork functions are generated based on the raw performancemeasurements (1504). In some examples, the one or more network functionsare NEFs (e.g., NEF 323), and the performance measurements are relatedto application triggering requested by an application function (e.g., AF328). In some examples, the one or more network functions are AMFs(e.g., AMF 321), and the performance measurements are related to shortmessage service (SMS) over non-access stratum (NAS). In some examples,the performance measurements are specified as part of a communicationstandard, such as a 3GPP standard (e.g., in 3GPP TS 28.552). In someexamples, the raw performance measurements are obtained and/or theperformance measurements are generated by a service producer that islocated, for example, in one of the one or more NEFs, AMFs, or anothermanagement function (e.g., of a core network 120, 220, 320). Thegenerated performance measurements can be stored, transmitted,displayed, or otherwise provided to end users (e.g., service consumers,UEs 101, 201, 301, users accessing exposure points of the core network120, 220, 320, etc.) in any suitable form.

In some examples, the performance measurements can include one or moreof a number of application trigger requests, a number of applicationtrigger requests accepted for delivery, a number of application triggerrequests rejected for delivery, a number of protocol data unit (PDU)sessions requested to modify, or a number of application triggerdelivery reports. The number of application trigger requests can bebased on a cumulative counter that is triggered on receipt of a deliveryrequest (e.g., a Nnef_Trigger_Delivery request) by a NEF from theapplication function. The number application trigger requests acceptedfor delivery can be based on a cumulative counter that is triggered ontransmission of a delivery response (e.g., a Nnef_trigger_Deliveryresponse) by a NEF to the application function, with the deliveryresponse including an indication that an application trigger request hasbeen accepted for delivery to a UE. The number of application triggerrequests rejected for delivery can be based on a cumulative counter thatis triggered on transmission of a delivery response (e.g., aNnef_Trigger_Delivery response) by a NEF to the application function,with the delivery response including an indication that an applicationtrigger request has been rejected for delivery to a UE. In someexamples, the number of application trigger requests rejected fordelivery is incremented per error code (e.g., per response code, asspecified in the 3GPP technical specifications). The number ofapplication trigger delivery reports can be based on a cumulativecounter that is triggered on transmission of a delivery message (e.g., aNnef_Trigger_Delivery Notify message) by a NEF to the applicationfunction, with the delivery message including an indication of adelivery result of an application trigger. In some examples, the numberof application trigger delivery reports is incremented per deliveryresult (e.g., success, failure, or another result specified in the 3GPPtechnical specifications).

In some examples, the performance measurements include one or more of anumber of registration requests for SMS over NAS, a number of successfulregistrations allowed for SMS over NAS, a number of attempted mobileoriginated (MO) SMS messages over NAS, a number of MO SMS messagessuccessfully transported over NAS, a number of attempted mobileterminated (MT) SMS messages over NAS, or a number of MT SMS messagessuccessfully transported over NAS.

The number of registration requests for SMS over NAS can be based on acumulative counter that is triggered on receipt of a registrationrequest message by an AMF from a UE, the registration request messageincluding an indication that the UE supports SMS delivery over NAS(e.g., “SMS supported,” as specified in 3GPP TS 23.502). The number ofsuccessful registrations allowed for SMS over NAS can be based on acumulative counter that is triggered on transmission of a registrationaccept message by an AMF to a UE, the registration accept messageincluding an indication that the SMS is allowed (e.g., “SMS allowed,” asspecified in 3GPP TS 23.502).

The number of attempted MO SMS messages over NAS can be based on acumulative counter that is triggered on receipt of a NAS message by anAMF from a UE, the NAS message including an indication of SMStransportation. The number of MO SMS messages successfully transportedover NAS can be based on a cumulative counter that is triggered ontransmission of a NAS message by an AMF to a UE, the NAS messageincluding an indication that the MO SMS message has been successfullydelivered.

The number of attempted MT SMS messages over NAS can be based on acumulative counter that is triggered on transmission of a NAS message byan AMF to a UE, the NAS message including an indication of SMStransportation. The number of MT SMS messages successfully transportedover NAS can be based on a cumulative counter that is triggered onreceipt of a NAS message by an AMF from a UE, the NAS message includingan indication that the MT SMS message has been successfully delivered.

In some examples, the performance measurements can be separated byaccess type (e.g., 3GPP access and non-3GPP access). In other examples,the performance measurements can be made without regard to the accesstype.

Some non-limiting examples are as follows. The following examplespertain to further embodiments, and specifics in the examples may beused anywhere in one or more embodiments discussed previously. Any ofthe following examples may be combined with any other example or anyembodiment discussed herein.

Example 1 may include a service producer supported by one or moreprocessors configured to: obtain the raw performance measurements fromNEF(s); and generate the performance measurements for NEF(s) based onthe raw performance measurements.

Example 2 may include the service producer of example 1 and/or someother example(s) herein, wherein the service producer is located in anNEF or a management function.

Example 3 may include the service producer of examples 1 and 2 and/orsome other example(s) herein, wherein the performance measurement isrelated to application triggering requested by AF.

Example 4 may include the service producer of example 3 and/or someother example(s) herein, wherein the performance measurement is numberof application trigger requests, number of application trigger requestsaccepted for delivery, number of application trigger requests rejectedfor delivery, number of PDU Sessions requested to modify, or number ofapplication trigger delivery reports.

Example 5 may include the service producer of example 4 or some otherexample herein, wherein: the performance measurement of number ofapplication trigger requests is a cumulative counter (CC) which istriggered on receipt of an Nnef_Trigger_Delivery request by the NEF fromAF; the performance measurement of number application trigger requestsaccepted for delivery is a CC which is triggered on transmission ofNnef_Trigger_Delivery response by the NEF to AF indicating theapplication trigger request has been accepted for delivery to the UE;the performance measurement of number of application trigger requestsrejected for delivery is a CC which is triggered on transmission of anNnef_Trigger_Delivery response by the NEF to AF indicating theapplication trigger request has been rejected for delivery to the UE;and the performance measurement of number of application triggerdelivery reports is a CC which is triggered on Transmission of anNnef_Trigger_DeliveryNotify message by the NEF to AF indicating thedelivery result of the application trigger.

Example 6 may include the service producer of examples 4 and 5 and/orsome other example(s) herein, wherein the performance measurement ofnumber of application trigger requests rejected for delivery isincremented to the relevant subcounter per error code.

Example 7 may include the service producer of examples 4 and 5 and/orsome other example(s) herein, wherein the performance measurement ofnumber of application trigger delivery reports is incremented to therelevant subcounter per delivery result.

Example 8 may include a service producer supported by one or moreprocessors configured to: obtain the raw performance measurements fromAMF(s); and generate the performance measurements for AMF(s) based onthe raw performance measurements.

Example 9 may include the service producer of example 8 and/or someother example(s) herein, wherein the service producer is located in anAMF or a management function.

Example 10 may include the service producer of examples 8 and 9 and/orsome other example(s) herein, wherein the performance measurement isrelated to SMS over NAS.

Example 11 may include the service producer of example 10 and/or someother example(s) herein, wherein the performance measurement is numberof registration requests for SMS over NAS, number of successfulregistrations allowed for SMS over NAS, number of attempted MO SMSmessages over NAS, number of MO SMS messages successfully transportedover NAS, number of attempted MT SMS messages over NAS, or number of MTSMS messages successfully transported over NAS.

Example 12 may include the service producer of example 11 and/or someother example(s) herein, wherein: the performance measurement of numberof registration requests for SMS over NAS is a CC which is triggered onreceipt of a Registration Request message containing the “SMS supported”indication indicating that the UE supports SMS delivery over NAS by theAMF from UE; the performance measurement of number of successfulregistrations allowed for SMS over NAS is a CC which is triggered ontransmission of a Registration Accept message containing the “SMSallowed” indication by the AMF to UE; the performance measurement ofnumber of attempted MO SMS messages over NAS is a CC which is triggeredon receipt of an NAS message with an indication of SMS transportation bythe AMF from UE; the performance measurement of number of MO SMSmessages successfully transported over NAS is a CC which is triggered ontransmission, by the AMF to UE, of an NAS message that contains the“submit report” indicating the MO SMS message has been successfullydelivered; the performance measurement of number of attempted MT SMSmessages over NAS is a CC which is triggered on transmission of an NASmessage with an indication of SMS transportation by the AMF to UE; theperformance measurement of number of MT SMS messages successfullytransported over NAS is a CC which is triggered on Receipt, by the AMFfrom UE, of an NAS message that contains the “delivery report”indicating the MT SMS message has been successfully delivered.

Example 13 may include the service producer of examples 10 and 11 and/orsome other example(s) herein, wherein the performance measurement is forthe case of SMS over NAS via 3GPP access.

Example 14 may include the service producer of examples 10 and 11 and/orsome other example(s) herein, wherein the performance measurement is forthe case of SMS over NAS via non-3GPP access.

Example 15 may include the service producer of example 13 and/or someother example(s) herein, wherein the messages triggering the counters ofexample 12 are received or sent via 3GPP access.

Example 16 may include the service producer of example 14 and/or someother example(s) herein, wherein the messages triggering the countersexample 12 are received or sent via non-3GPP access.

Example 17 may include a method to be performed by a service producer,the method comprising: obtaining or causing to obtain raw performancemeasurements from one or more NFs; and generating or causing to generateperformance measurements (or performance indicators) for the one or moreNFs based on the raw performance measurements.

Example 18 may include the method of example 17 and/or some otherexample(s) herein, wherein the one or more NFs are NEFs.

Example 19 may include the method of example 18 and/or some otherexample(s) herein, wherein the service producer is located in one of theone or more NEFs or a management function.

Example 20 may include the method of examples 18 and 19 and/or someother example(s) herein, wherein the generated performance measurementsare related to application triggering requested by an AF.

Example 21 may include the method of example 20 and/or some otherexample(s) herein, wherein the performance measurements include one ormore of a number of application trigger requests, a number ofapplication trigger requests accepted for delivery, a number ofapplication trigger requests rejected for delivery, a number of PDUSessions requested to modify, and/or a number of application triggerdelivery reports.

Example 22 may include the method of example 21 and/or some otherexample(s) herein, wherein the number of application trigger requests isbased on a CC that is triggered on receipt of a Nnef_Trigger_Deliveryrequest by the NEF from the AF.

Example 23 may include the method of examples 21 to 22 and/or some otherexample(s) herein, wherein the number application trigger requestsaccepted for delivery is based on a CC that is triggered on transmissionof Nnef_Trigger_Delivery response by the NEF to the AF indicating theapplication trigger request has been accepted for delivery to a UE.

Example 24 may include the method of examples 21 to 23 and/or some otherexample(s) herein, wherein the number of application trigger requestsrejected for delivery is based on a CC that is triggered on transmissionof an Nnef_Trigger_Delivery response by the NEF to the AF indicating theapplication trigger request has been rejected for delivery to a UE.

Example 25 may include the method of example 24 and/or some otherexample(s) herein, wherein the number of application trigger requestsrejected for delivery is incremented to the relevant subcounter pererror code.

Example 26 may include the method of examples 21 to 25 and/or some otherexample(s) herein, wherein the number of application trigger deliveryreports is based on a CC that is triggered on Transmission of anNnef_Trigger_DeliveryNotify message by the NEF to the AF indicating thedelivery result of the application trigger.

Example 27 may include the method of example 26 and/or some otherexample(s) herein, wherein the number of application trigger deliveryreports is incremented to the relevant subcounter per delivery result.

Example 28 may include the method of example 17 and/or some otherexample(s) herein, wherein the one or more NFs are AMFs.

Example 29 may include the method of example 28 and/or some otherexample(s) herein, wherein the service producer is located in one of theone or more AMFs or a management function.

Example 30 may include the method of examples 28 or 29 and/or some otherexample(s) herein, wherein the generated performance measurements arerelated to SMS over NAS.

Example 31 may include the method of example 30 and/or some otherexample(s) herein, wherein the performance measurements include one ormore of a number of registration requests for SMS over NAS, a number ofsuccessful registrations allowed for SMS over NAS, a number of attemptedMO SMS messages over NAS, a number of MO SMS messages successfullytransported over NAS, a number of attempted MT SMS messages over NAS,and/or a number of MT SMS messages successfully transported over NAS.

Example 32 may include the method of example 31 and/or some otherexample(s) herein, wherein the number of registration requests for SMSover NAS is a CC that is triggered on receipt of a Registration Requestmessage containing the “SMS supported” indication indicating that the UEsupports SMS delivery over NAS by the AMF from a UE.

Example 33 may include the method of examples 31 or 32 and/or some otherexample(s) herein, wherein the number of successful registrationsallowed for SMS over NAS is a CC that is triggered on transmission of aRegistration Accept message containing the “SMS allowed” indication bythe AMF to a UE.

Example 34 may include the method of examples 31 to 33 and/or some otherexample(s) herein, wherein the number of attempted MO SMS messages overNAS is a CC that is triggered on receipt of an NAS message with anindication of SMS transportation by the AMF from a UE.

Example 35 may include the method of examples 31 to 34 and/or some otherexample(s) herein, wherein the number of MO SMS messages successfullytransported over NAS is a CC that is triggered on transmission, by theAMF to UE, of an NAS message that contains the “submit report”indicating the MO SMS message has been successfully delivered.

Example 36 may include the method of examples 31 to 35 and/or some otherexample(s) herein, wherein the number of attempted MT SMS messages overNAS is a CC that is triggered on transmission of an NAS message with anindication of SMS transportation by the AMF to a UE.

Example 37 may include the method of examples 31 to 36 and/or some otherexample(s) herein, wherein the number of MT SMS messages successfullytransported over NAS is a CC that is triggered on Receipt, by the AMFfrom a UE, of an NAS message that contains the “delivery report”indicating the MT SMS message has been successfully delivered.

Example 38 may include the method of examples 31 to 37 and/or some otherexample(s) herein, wherein the performance measurement is for the caseof SMS over NAS via 3GPP access.

Example 39 may include the method of example 38 and/or some otherexample(s) herein, wherein the messages triggering the CCs are receivedor sent via 3GPP access.

Example 40 may include the method of examples 31 to 39 and/or some otherexample(s) herein, wherein the performance measurement is for the caseof SMS over NAS via non-3GPP access.

Example 41 may include the method of example 40 and/or some otherexample(s) herein, wherein the messages triggering the CCs are receivedor sent via non-3GPP access.

Example 42 may include an apparatus comprising means to perform one ormore elements of a method described in or related to any of examples 1to 41, or any other method or process described herein.

Example 43 may include one or more non-transitory computer-readablemedia comprising instructions to cause an electronic device, uponexecution of the instructions by one or more processors of theelectronic device, to perform one or more elements of a method describedin or related to any of examples 1 to 41, or any other method or processdescribed herein.

Example 44 may include an apparatus comprising logic, modules, orcircuitry to perform one or more elements of a method described in orrelated to any of examples 1 to 41, or any other method or processdescribed herein.

Example 45 may include a method, technique, or process as described inor related to any of examples 1 to 41, or portions or parts thereof.

Example 46 may include an apparatus comprising: one or more processorsand one or more computer-readable media comprising instructions that,when executed by the one or more processors, cause the one or moreprocessors to perform the method, techniques, or process as described inor related to any of examples 1 to 41, or portions thereof.

Example 47 may include a signal as described in or related to any ofexamples 1 to 41, or portions or parts thereof.

Example 48 may include a datagram, packet, frame, segment, protocol dataunit (PDU), or message as described in or related to any of examples 1to 41, or portions or parts thereof, or otherwise described in thepresent disclosure.

Example 49 may include a signal encoded with data as described in orrelated to any of examples 1 to 41, or portions or parts thereof, orotherwise described in the present disclosure.

Example 50 may include a signal encoded with a datagram, packet, frame,segment, protocol data unit (PDU), or message as described in or relatedto any of examples 1 to 41, or portions or parts thereof, or otherwisedescribed in the present disclosure.

Example 51 may include an electromagnetic signal carryingcomputer-readable instructions, wherein execution of thecomputer-readable instructions by one or more processors is to cause theone or more processors to perform the method, techniques, or process asdescribed in or related to any of examples 1 to 41, or portions thereof.

Example 52 may include a computer program comprising instructions,wherein execution of the program by a processing element is to cause theprocessing element to carry out the method, techniques, or process asdescribed in or related to any of examples 1 to 41, or portions thereof.

Example 53 may include a signal in a wireless network as shown anddescribed herein.

Example 54 may include a method of communicating in a wireless networkas shown and described herein.

Example 55 may include a system for providing wireless communication asshown and described herein.

Example 56 may include a device for providing wireless communication asshown and described herein.

It is well understood that the use of personally identifiableinformation should follow privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining the privacy of users. In particular,personally identifiable information data should be managed and handledso as to minimize risks of unintentional or unauthorized access or use,and the nature of authorized use should be clearly indicated to users.

The methods described here may be implemented in software, hardware, ora combination thereof, in different implementations. In addition, theorder of the blocks of the methods may be changed, and various elementsmay be added, reordered, combined, omitted, modified, and the like.Various modifications and changes may be made as would be obvious to aperson skilled in the art having the benefit of this disclosure. Thevarious implementations described here are meant to be illustrative andnot limiting. Many variations, modifications, additions, andimprovements are possible. Accordingly, plural instances may be providedfor components described here as a single instance. Boundaries betweenvarious components, operations and data stores are somewhat arbitrary,and particular operations are illustrated in the context of specificillustrative configurations. Other allocations of functionality areenvisioned and may fall within the scope of claims that follow. Finally,structures and functionality presented as discrete components in theexample configurations may be implemented as a combined structure orcomponent.

The following terms and definitions may be applicable to the examplesdescribed herein.

The term “circuitry” as used herein refers to, is part of, or includeshardware components such as an electronic circuit, a logic circuit, aprocessor (shared, dedicated, or group) and/or memory (shared,dedicated, or group), an Application Specific Integrated Circuit (ASIC),a field-programmable device (FPD) (e.g., a field-programmable gate array(FPGA), a programmable logic device (PLD), a complex PLD (CPLD), ahigh-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC),digital signal processors (DSPs), etc., that are configured to providethe described functionality. In some embodiments, the circuitry mayexecute one or more software or firmware programs to provide at leastsome of the described functionality. The term “circuitry” may also referto a combination of one or more hardware elements (or a combination ofcircuits used in an electrical or electronic system) with the programcode used to carry out the functionality of that program code. In theseembodiments, the combination of hardware elements and program code maybe referred to as a particular type of circuitry.

The term “processor circuitry” as used herein refers to, is part of, orincludes circuitry capable of sequentially and automatically carryingout a sequence of arithmetic or logical operations, or recording,storing, and/or transferring digital data. The term “processorcircuitry” may refer to one or more application processors, one or morebaseband processors, a physical central processing unit (CPU), asingle-core processor, a dual-core processor, a triple-core processor, aquad-core processor, and/or any other device capable of executing orotherwise operating computer-executable instructions, such as programcode, software modules, and/or functional processes. The terms“application circuitry” and/or “baseband circuitry” may be consideredsynonymous to, and may be referred to as, “processor circuitry.”

The term “interface circuitry” as used herein refers to, is part of, orincludes circuitry that enables the exchange of information between twoor more components or devices. The term “interface circuitry” may referto one or more hardware interfaces, for example, buses, U/O interfaces,peripheral component interfaces, network interface cards, and/or thelike.

The term “user equipment” or “UE” as used herein refers to a device withradio communication capabilities and may describe a remote user ofnetwork resources in a communications network. The term “user equipment”or “UE” may be considered synonymous to, and may be referred to as,client, mobile, mobile device, mobile terminal, user terminal, mobileunit, mobile station, mobile user, subscriber, user, remote station,access agent, user agent, receiver, radio equipment, reconfigurableradio equipment, reconfigurable mobile device, etc. Furthermore, theterm “user equipment” or “UE” may include any type of wireless/wireddevice or any computing device including a wireless communicationsinterface.

The term “network element” as used herein refers to physical orvirtualized equipment and/or infrastructure used to provide wired orwireless communication network services. The term “network element” maybe considered synonymous to and/or referred to as a networked computer,networking hardware, network equipment, network node, router, switch,hub, bridge, radio network controller, RAN device, RAN node, gateway,server, virtualized VNF, NFVI, and/or the like.

The term “computer system” as used herein refers to any typeinterconnected electronic devices, computer devices, or componentsthereof. Additionally, the term “computer system” and/or “system” mayrefer to various components of a computer that are communicativelycoupled with one another. Furthermore, the term “computer system” and/or“system” may refer to multiple computer devices and/or multiplecomputing systems that are communicatively coupled with one another andconfigured to share computing and/or networking resources.

The term “appliance,” “computer appliance,” or the like, as used hereinrefers to a computer device or computer system with program code (e.g.,software or firmware) that is specifically designed to provide aspecific computing resource. A “virtual appliance” is a virtual machineimage to be implemented by a hypervisor-equipped device that virtualizesor emulates a computer appliance or otherwise is dedicated to provide aspecific computing resource.

The term “element” refers to a unit that is indivisible at a given levelof abstraction and has a clearly defined boundary, wherein an elementmay be any type of entity including, for example, one or more devices,systems, controllers, network elements, modules, etc., or combinationsthereof.

The term “device” refers to a physical entity embedded inside, orattached to, another physical entity in its vicinity, with capabilitiesto convey digital information from or to that physical entity.

The term “entity” refers to a distinct component of an architecture ordevice, or information transferred as a payload.

The term “controller” refers to an element or entity that has thecapability to affect a physical entity, such as by changing its state orcausing the physical entity to move.

The term “resource” as used herein refers to a physical or virtualdevice, a physical or virtual component within a computing environment,and/or a physical or virtual component within a particular device, suchas computer devices, mechanical devices, memory space, processor/CPUtime, processor/CPU usage, processor and accelerator loads, hardwaretime or usage, electrical power, input/output operations, ports ornetwork sockets, channel/link allocation, throughput, memory usage,storage, network, database and applications, workload units, and/or thelike. A “hardware resource” may refer to compute, storage, and/ornetwork resources provided by physical hardware element(s). A“virtualized resource” may refer to compute, storage, and/or networkresources provided by virtualization infrastructure to an application,device, system, etc. The term “network resource” or “communicationresource” may refer to resources that are accessible by computerdevices/systems via a communications network. The term “systemresources” may refer to any kind of shared entities to provide services,and may include computing and/or network resources. System resources maybe considered as a set of coherent functions, network data objects orservices, accessible through a server where such system resources resideon a single host or multiple hosts and are clearly identifiable.

The term “channel” as used herein refers to any transmission medium,either tangible or intangible, which is used to communicate data or adata stream. The term “channel” may be synonymous with and/or equivalentto “communications channel,” “data communications channel,”“transmission channel,” “data transmission channel,” “access channel,”“data access channel,” “link,” “data link,” “carrier,” “radiofrequencycarrier,” and/or any other like term denoting a pathway or mediumthrough which data is communicated. Additionally, the term “link” asused herein refers to a connection between two devices through a RAT forthe purpose of transmitting and receiving information.

The term “communication protocol” (either wired or wireless) refers to aset of standardized rules or instructions implemented by a communicationdevice and/or system to communicate with other devices and/or systems,including instructions for packetizing/depacketizing data,modulating/demodulating signals, implementation of protocols stacks,and/or the like.

The terms “instantiate,” “instantiation,” and the like as used hereinrefers to the creation of an instance. An “instance” also refers to aconcrete occurrence of an object, which may occur, for example, duringexecution of program code.

The terms “coupled,” “communicatively coupled,” along with derivativesthereof are used herein. The term “coupled” may mean two or moreelements are in direct physical or electrical contact with one another,may mean that two or more elements indirectly contact each other butstill cooperate or interact with each other, and/or may mean that one ormore other elements are coupled or connected between the elements thatare said to be coupled with each other. The term “directly coupled” maymean that two or more elements are in direct contact with one another.The term “communicatively coupled” may mean that two or more elementsmay be in contact with one another by a means of communication includingthrough a wire or other interconnect connection, through a wirelesscommunication channel or ink, and/or the like.

The term “information element” refers to a structural element containingone or more fields. The term “field” refers to individual contents of aninformation element, or a data element that contains content.

The term “admission control” refers to a validation process incommunication systems where a check is performed before a connection isestablished to see if current resources are sufficient for the proposedconnection.

The term “IP Latency” is the time it takes to transfer a first/initialpacket in a data burst from one point to another

The term “Mapped 5QI” refers to a 5G QoS identifier (5QI) that is usedfor a data radio bearer (DRB) within the gNB when a single 5QI isassigned to the DRB, and/or a 5QI that is used for separating certainmeasurements per QoS class. Individual QoS flows into a common 5QI isspecified in 3GPP TS 38.473.

The term “Packet Delay” refers to the time it takes to transfer anypacket from one point to another.

The term “Packet Drop Rate” refers to a share of packets that were notsent to the target due to high traffic load or traffic management andshould be seen as a part of the packet loss rate.

The term “Packet Loss Rate” refers to a share of packets that could notbe received by the target, including packets dropped, packets lost intransmission and packets received in wrong format.

The term “Performance Indicators” refers to performance data aggregatedover one or more NFs which is derived from the performance measurementscollected at the NF(s), according to the aggregation method identifiedin the Performance Indicator definition.

The term “SMTC” refers to an SSB-based measurement timing configurationconfigured by SSB-MeasurementTimingConfiguration.

The term “SSB” refers to an SS/PBCH block.

The term “a “Primary Cell” refers to the MCG cell, operating on theprimary frequency, in which the UE either performs the initialconnection establishment procedure or initiates the connectionre-establishment procedure.

The term “Primary SCG Cell” refers to the SCG cell in which the UEperforms random access when performing the Reconfiguration with Syncprocedure for DC operation.

The term “Secondary Cell” refers to a cell providing additional radioresources on top of a Special Cell for a UE configured with CA.

The term “Secondary Cell Group” refers to the subset of serving cellscomprising the PSCell and zero or more secondary cells for a UEconfigured with DC.

The term “Serving Cell” refers to the primary cell for a UE inRRC_CONNECTED not configured with CA/DC there is only one serving cellcomprising of the primary cell.

The term “serving cell” or “serving cells” refers to the set of cellscomprising the Special Cell(s) and all secondary cells for a UE inRRC_CONNECTED configured with CA/DC.

The term “Special Cell” refers to the PCell of the MCG or the PSCell ofthe SCG for DC operation; otherwise, the term “Special Cell” refers tothe Pcell.

What is claimed is:
 1. A method, comprising: obtaining performance datafrom one or more network functions in a wireless communication network,the one or more network functions including at least one of a networkexposure function (NEF) or an access and mobility management function(AMF); and performing measurements for the one or more network functionsbased at least in part on the performance data, wherein at least one ofthe measurements is to increment a subcounter per error code by a numberof requests rejected for delivery by the one or more network functions.2. The method of claim 1, wherein the one or more network functionsinclude the NEF, and wherein the measurements are related to applicationtriggering requested by an application function.
 3. The method of claim2, wherein the measurements include one or more of a number ofapplication trigger requests, a number of application trigger requestsaccepted for delivery, a number of protocol data unit (PDU) sessionsrequested to modify, or a number of application trigger deliveryreports.
 4. The method of claim 3, wherein the number of applicationtrigger requests is based on a cumulative counter that is triggered onreceipt of a delivery request by the NEF from the application function.5. The method of claim 3, wherein the number application triggerrequests accepted for delivery is based on a cumulative counter that istriggered on transmission of a delivery response by the NEF to theapplication function, the delivery response including an indication thatan application trigger request has been accepted for delivery to a userequipment (UE).
 6. The method of claim 2, wherein the number of requestsrejected for delivery comprises a number of application trigger requestsrejected for delivery, and wherein the number of application triggerrequests rejected for delivery is based on a cumulative counter that istriggered on transmission of a delivery response by the NEF to theapplication function, the delivery response including an indication thatan application trigger request has been rejected for delivery to a userequipment (UE).
 7. The method of claim 6, wherein the number ofapplication trigger requests rejected for delivery is split intosubcounters per error code, and wherein the number of applicationtrigger requests rejected for delivery is incremented to a relevant oneof the subcounters per error code.
 8. The method of claim 3, wherein thenumber of application trigger delivery reports is based on a cumulativecounter that is triggered on transmission of a delivery message by theNEF to the application function, the delivery message including anindication of a delivery result of an application trigger.
 9. The methodof claim 8, wherein the number of application trigger delivery reportsis incremented per delivery result.
 10. The method of claim 1, whereinthe one or more network functions include the AMF, and wherein themeasurements are related to short message service (SMS) over non-accessstratum (NAS).
 11. The method of claim 10, wherein the measurementsinclude one or more of a number of registration requests for SMS overNAS, a number of successful registrations allowed for SMS over NAS, anumber of attempted mobile originated (MO) SMS messages over NAS, anumber of MO SMS messages successfully transported over NAS, a number ofattempted mobile terminated (MT) SMS messages over NAS, or a number ofMT SMS messages successfully transported over NAS.
 12. The method ofclaim 11, wherein the number of registration requests for SMS over NASis based on a cumulative counter that is triggered on receipt of aregistration request message by the AMF from a user equipment (UE), theregistration request message including an indication that the UEsupports SMS delivery over NAS.
 13. The method of claim 11, wherein thenumber of successful registrations allowed for SMS over NAS is based ona cumulative counter that is triggered on transmission of a registrationaccept message by the AMF to a user equipment (UE), the registrationaccept message including an indication that the SMS is allowed.
 14. Themethod of claim 11, wherein the number of attempted MO SMS messages overNAS is based on a cumulative counter that is triggered on receipt of aNAS message by the AMF from a user equipment (UE), the NAS messageincluding an indication of SMS transportation.
 15. The method of claim11, wherein the number of MO SMS messages successfully transported overNAS is based on a cumulative counter that is triggered on transmissionof a NAS message by the AMF to a user equipment (UE), the NAS messageincluding an indication that the MO SMS message has been successfullydelivered.
 16. The method of claim 11, wherein the number of attemptedMT SMS messages over NAS is based on a cumulative counter that istriggered on transmission of a NAS message by the AMF to a userequipment (UE), the NAS message including an indication of SMStransportation.
 17. The method of claim 11, wherein the number of MT SMSmessages successfully transported over NAS is based on a cumulativecounter that is triggered on receipt of a NAS message by the AMF from auser equipment (UE), the NAS message including an indication that the MTSMS message has been successfully delivered.
 18. The method of claim 11,wherein the measurements comprise first measurements for SMS over NASvia 3GPP access and second measurements for SMS over NAS via non-3GPPaccess.
 19. A processor for a telecommunications device, the processorcomprising: circuitry to execute one or more instructions stored in astorage device that, when executed, cause the processor to performoperations comprising: obtaining performance data from one or morenetwork functions in a wireless communication network, the one or morenetwork functions including at least one of a network exposure function(NEF) or an access and mobility management function (AMF); andperforming measurements for the one or more network functions based atleast in part on the performance data, wherein at least one of themeasurements is to increment a subcounter per error code by a number ofrequests rejected for delivery by the one or more network functions. 20.A non-transitory computer readable storage medium storing instructionswhich, when executed by one or more processors, cause the one or moreprocessors to perform operations comprising: obtaining performance datafrom one or more network functions in a wireless communication network,the one or more network functions including at least one of a networkexposure function (NEF) or an access and mobility management function(AMF); and performing measurements for the one or more network functionsbased at least in part on the performance data, wherein at least one ofthe measurements is to increment a subcounter per error code by a numberof requests rejected for delivery by the one or more network functions.